Grant Ingersoll pisze:
> Hi Fellow Aperturians,
> Is there any place that one can subscribe to commit messages from
> SVN? If not, is there anyway to send them to the dev list or some
> newly created list? As much as I hate the thought of more mail, it
> would be useful as a means of keeping up with things. I don't want to
> track the source, but I do want to be more in the know of what is
> coming down the pike, as they say.
Sourceforge allows projects to attach a commit hook on the SVN repo that
sends commit notifications. We can turn it on. It may actually be a good
motivational tool to keep the commits clear and focussed on a specific
> I'm not sure what SourceForge offers for issue tracking, patches, etc.
> but the Aperture community might consider adopting a patch and commit
> mentality, whereby patches/changes are posted to a public facing issue
> and then committed. I think this would encourage the community as a
> whole to offer patches (by showing them how it is done) and allow
> individuals to get specific patches that can then be applied to
> specific versions without having to parse out the trunk changes. Just
> as an example (and it isn't the only way to do things), in Lucene, as
> committers, we pretty much open an issue and attach a patch for pretty
> much every change we make, with the exception of minor typo/
> documentation errors. I think it also would give the sense the
> community has a say in the development b/c they can comment on
> patches, try them out, test them, etc. and it isn't just a few people
> throwing code over the wall. We should also consider encouraging
> outside contributions via something like: http://wiki.apache.org/lucene-java/HowToContribute
> In fact, I would consider adding it to the front landing page.
> We might also consider elucidating how one becomes a committer on
> Aperture (doesn't have to be formal, but should at least be stated) if
> that is something the project would consider (I would hope it does, I
> think it is vital for the community. Note, I am not lobbying for me
> to be committer, as I haven't contributed in that way and frankly
> don't have the time. This is what Mahout does: http://cwiki.apache.org/MAHOUT/howtobecomeacommitter.html)
> I hope this isn't seen as critical in anyway. I truly feel Aperture
> has a lot to offer and would like to see the community grow more.
> FWIW, patches can usually be created by:
> In the base directory:
> svn diff > myGreatPatch.patch
> Then, to apply the patch:
> patch -p 0 -i myGreatPatch.patch [--dry-run]
> to apply it, or use --dry-run to try it out w/o changing anything.
I subscribe to all you said with both my hands and feet. A proper commit
review process would be beneficial for everyone. Reviews and testing are
critical for Aperture stability. You can't mock an IMAP server, or an
Outlook instance. All of this needs to be tested and if every patch runs
on two machines makes it is much more likely that it's good than if it
runs on only one machine.
In the long term, I guess it's time for Aperture to focus more on
improving the quality, stability and performance. In order to achieve
these goals the entire community needs to cooperate. We need to lower
the barriers of entry.
We've been brainstorming ideas for Aperture 2.0, a cleanup of all the
residue that has accumulated in two years of organic growth. This may be
a good opportunity to improve the development process.