2011/5/10 Greg Troxel <g...@ir.bbn.com>:
>
> Robert Norris <rw_nor...@hotmail.com> writes:
>
>>> It looks like Rob is now working directly in the SF repo.
>>
>> Since I have commit privileges, 'simple' fixes / small changes get
>> applied directly to the SF repo.
>> This is a maintainer thing as they don't necessarily need any feedback
>> before being applied.
>
> That's totally fine - I didn't mean to be critical of it.  I was just
> trying to figure out which repo to follow.

Yes, it's true that this information is missing in source package.
Even DOAP file does not contain the reference to the "official" Git
repo (yes, Sourceforge hosted Git repo is currently the official one).

>>> I'd like to see a HACKING.git in the official repo that lists all the
>>> URLs of actively-maintained versions.   Sort of like a list of forks,
>>> but without buying ito any repo service as the one true way.
>>>
>>> So, can people explain what counts these days?
>>
>> I don't think this needs to be in the source, perhaps in the Wiki -
>> contribute' part.
>
> It's vastly more important to be somewhere, of course, and that seems
> fine.  Even after logging in to sourceforge (I am 'lexort'), there's no
> edit tab.
>
> My preference for being in the source comes from 1) me being from the
> pre-wiki generation and 2) it follows git's notion of distributed
> version control and local operations - so having a clone means you have
> all the data.

I'm finally fully agree with Greg. Initialy I imagined that whole
documentation should be in the wiki. But I revised my opinion. I vote
for having as much information in text files in the code.
The main reason is that it ensure that documentation/information is
always in sync with code and hackers will have hability to fork (even
us if we decide to leave Sourceforge one day).

The wiki should (probably) serve two goals (at least):
- website, advertising about viking
- community site, to share map sources or enumerate personnal forks of
the Git repo.

So please, add the Git repo URL and contribution conventions to HACKING file.


-- 
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/

Reply via email to