[uf-dev] Re: hReview creator broken + what source control do
people prefer?
Ben Ward
lists at ben-ward.co.uk
Wed May 13 17:52:03 PDT 2009
On 13 May 2009, at 17:22, Manu Sporny wrote:
> Tantek Çelik wrote:
>> Would moving from Mercurial hosted on microformats.org to github.com
>> (or another system/location) help/encourage folks to participate more
>> in microformats open source projects?
>
> +1 - We use git extensively at our company. I'd certainly be more
> interested and would contribute the 'microformalyze' application that
> was used to analyze webpages for hAudio.
I also favour github; it's lovely. More specifically, I favour us
getting out of the business of running our own repository. It's not
well exposed, and dedicated parties (Github, Launchpad, Google Code
etc.) provide better tools that we simply don't have the time to
maintain. Plus, they're far better exposed to a wider developer
community.
The way things stand, we reserve the ‘microformats’ accounts on most
of those sites. Github's model is especially sweet, in that we can use
that account to watch/fork other projects for aggregation purposes,
whilst the work is done by the original authors. It seems very well
suited.
I think my favoured solution is:
* Get code off hg.microformats, onto whatever platform the
maintainer prefers (Git, Bzr, Svn, whatever)
* Use accounts on those services to provide service-level
aggregation for convenient, but more agnostically:
* Get the wiki in order so people can find the projects regardless
of where they are. I think http://microformats.org/wiki/parsers could
be formatted a little differently to link to ‘Project homepages’ as
well as ‘source code’, provide short summaries as a launchpad for
people to get involved. Potentially a new ‘/projects’ page to include
non-parser code.
That would mean: Brian Suda's X2V, and also various testcases, the
latter of which most definitely need better exposure and maintenance.
In the case of Manu's Microformatyze, we can get the /microformats
account to list it.
It shouldn't matter to us what code hosting project creators use, we
should just better encourage participation.
B
More information about the microformats-dev
mailing list