Indie-resource services

[a_bertrand]

I think indie-resource could benefit from a few services:
- Repositories for open source and non (like sourceforge or github but allows for private / group only projects).
- Marketplace to sell codes / services / content / art
- Advert section where you could post your requests or offers of services
- A "CLEAR" button to grab the list of new threads available on all pages, as well as "mark as read" button. Sorry but this is usual in any forums... yet I fail to find those here (new threads appear only in one are not in the others, and mark as read? No clues where it could be)
- A real time chat, yes I offered wsirc which for some of you didn't worked out, then propose an alternative.
- A tutorial / article section, outside of the forums where people can find / read those. It's a shame good content get buried inside the forums and new comers simply miss it.
- Hosting solutions (links to other sites or self offering?)
- Project list (who does what, and current progress and list of threads related?)
- A wiki which could grow about how to create a game?

Of course that's a lot of things, and not all are small to implement. But at least those are my current ideas of how to improve the value of this site / community.

[vitinho444]

Yeah i agree, my suggestion is to focus first on the Resource website and then we can start the so-feared community project to create those services.

I do think 2000 members is a little short for the awesome IR world, but i guess with milions we couldn't even talk in a offtopic thread

[hallsofvallhalla]

I like those ideas and look forward to everyones discussion and suggestions on them.

[Jackolantern]

Nice suggestions! We could set up our own git server or something like that, so it would use the familiar git commands but would allow private repositories without paying anything.

[a_bertrand]

I really wonder why everyone is after git. I don't like much git, I don't see much the benefits in git over SVN where actually many things don't work all that well in git. The only real advantage of git is thee branching and merging which I never use.

[Jackolantern]

I am not the hugest fan of it, but it is simple to learn, simple to setup and most implementations use a pretty standard API. If there is a good, easy-to-use (remember many people on here are fairly new to programming), open source SVN server that we could safely make public that would allow people to set up and manage their own projects, I would say that is fine, too. Most of the ones I have messed with have really been more for in-house use.

[a_bertrand]

For the client part tortoise SVN works very well. SVN integration in visual studio is perfect via Ankh SVN. And for the server? Any Linux distro offer SVN out of the box (yum install svn)

SVN is MUCH simpler to user than GIT, you don't need to commit and then to push your changes to the master repo. Also, SVN allows out of the box control per directory, while GIT requires commercial softs for it. SVN allows to take only part of a repository while GIT normally you would get the whole. Taking data from SVN is actually taking only the last file version, for GIT it is all the history as well (which make it slow). Overall the experience with SVN for me is much better than with GIT. Sure GIT do have its pro... but nothing I personally need or want.

[Nerfintas]

its a good idea with wiki, i know many tricks with dat and i could help

[hallsofvallhalla]

We use to have a wiki but it was never used.

[Xaleph]

Oh on the Git vs SVN thing, GIT is much easier to maintain, especially in large codebases. The biggest difference between the two is the fact that the server does not store all the branches. In fact, GIT stores all branches locally as well. It`s all binary data, while SVN requires the server to make changes and push and pull requests, GIT does not. It totally works on your local file system, the server is there for additional storage and sharing functionality ( sharing.. blegh, even that is possible without a server).

In any case, GIT runs local as well as online, SVN requires the server, thus creating dependencies.