From: Grant I. <gsi...@ap...> - 2008-05-14 18:13:37
|
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. 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. Cheers, Grant |
From: Antoni M. <ant...@gm...> - 2008-05-14 23:58:54
|
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 issue. > 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. Antoni Mylka ant...@gm... |
From: Grant I. <gsi...@ap...> - 2008-05-15 10:55:31
|
On May 14, 2008, at 7:58 PM, Antoni Myłka wrote: > Grant Ingersoll pisze: > 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. > Very cool. I'd also encourage you to do (almost all of) this brainstorming and the related decisions on the mailing list. Is it harder? Yes. Is it better for the community? Without a doubt. Frankly, I don't know that I, personally, would remain a user without it. I know it is easier to IM, phone or email internally amongst the committers, but it does more harm than good to the long term viability of the project. By doing it in the open, there is a public record we all can be a part of and their is an archive for answering questions later. Not too mention we will no doubt get lots of other good input from people. Cheers, Grant |
From: Antoni M. <ant...@gm...> - 2008-05-15 11:59:31
|
Grant Ingersoll pisze: > On May 14, 2008, at 7:58 PM, Antoni Myłka wrote: > >> Grant Ingersoll pisze: >> 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. >> > > Very cool. I'd also encourage you to do (almost all of) this > brainstorming and the related decisions on the mailing list. Is it > harder? Yes. Is it better for the community? Without a doubt. > Frankly, I don't know that I, personally, would remain a user without > it. I know it is easier to IM, phone or email internally amongst the > committers, but it does more harm than good to the long term viability > of the project. By doing it in the open, there is a public record we > all can be a part of and their is an archive for answering questions > later. Not too mention we will no doubt get lots of other good input > from people. > This brainstorm occurs on a public wiki page without any access restrictions: http://aperture.wiki.sourceforge.net/ApertureArchitectureCleanup which has a history http://aperture.wiki.sourceforge.net/page/history/ApertureArchitectureCleanup It has been advertised on this list a while ago, but you, as one of the most active Aperture community members are not aware of it, which means that our information policy sucks... :) You are right, we need to integrate: mailing list sourceforge fora tracker items (bugs and feature requests, both issues and comments) wiki changes Right now I use the following - subscribed to the mailing list - monitoring the fora (get notifications about new msgs) - afaik there is no way to get notified about all tracker activity I only get notifications on items submitted or assigned to me - there is an RSS feed with wiki changes http://aperture.wiki.sourceforge.net/space/xmla?v=rss_2_0 I guess we are small enough to channel all of this to a single mailing list. We had problems with tracker discussions because they got lost in the void, sourceforge doesn't allow to specify a cc list for an issue (the way trac does), doesn't provide RSS feeds of ALL tracker activity (like the trac does), only of single issues. AFAIK there are no email notifications from the wiki (viva la trac timeline). We will investigate into this, but after the release :) Antoni Mylka ant...@gm... |
From: Antoni M. <ant...@gm...> - 2008-05-15 12:00:36
|
Antoni Myłka pisze: > > You are right, we need to integrate: > > mailing list > sourceforge fora > tracker items (bugs and feature requests, both issues and comments) > wiki changes ... and SVN commits of course. Antoni Mylka ant...@gm... |
From: Grant I. <gsi...@ap...> - 2008-05-15 12:54:12
|
On May 15, 2008, at 7:59 AM, Antoni Myłka wrote: > > This brainstorm occurs on a public wiki page without any access > restrictions: > > http://aperture.wiki.sourceforge.net/ApertureArchitectureCleanup > > which has a history > > http://aperture.wiki.sourceforge.net/page/history/ApertureArchitectureCleanup > > It has been advertised on this list a while ago, but you, as one of > the > most active Aperture community members are not aware of it, which > means > that our information policy sucks... :) I don't know that I would assume that it sucks. I have a lot of optimizations setup in my mail reading workflow, so I tend to favor mail over all other forms and favor it's "push" model versus me remembering to visit a site on a regular basis, but that is just me. It _might_ be possible to have changes on the wiki send a diff email to the commits mailing list (once it exists.) In some sense, a change to the wiki is a "commit". > > > You are right, we need to integrate: > > mailing list > sourceforge fora > tracker items (bugs and feature requests, both issues and comments) > wiki changes > > Right now I use the following > - subscribed to the mailing list > - monitoring the fora (get notifications about new msgs) > - afaik there is no way to get notified about all tracker activity > I only get notifications on items submitted or assigned to me > - there is an RSS feed with wiki changes > http://aperture.wiki.sourceforge.net/space/xmla?v=rss_2_0 That I can deal with, I will subscribe to the RSS in my mail client. Thanks! > > > I guess we are small enough to channel all of this to a single mailing > list. We had problems with tracker discussions because they got lost > in > the void, sourceforge doesn't allow to specify a cc list for an issue > (the way trac does), doesn't provide RSS feeds of ALL tracker activity > (like the trac does), only of single issues. AFAIK there are no email > notifications from the wiki (viva la trac timeline). > > We will investigate into this, but after the release :) Agreed! |
From: Christiaan F. <chr...@ad...> - 2008-05-15 12:55:07
|
Antoni Myłka wrote: > You are right, we need to integrate: > > mailing list > sourceforge fora > tracker items (bugs and feature requests, both issues and comments) > wiki changes We have a forum? ;) Regards, Chris -- |
From: Antoni M. <ant...@gm...> - 2008-05-15 13:03:31
|
Christiaan Fluit pisze: > Antoni Myłka wrote: >> You are right, we need to integrate: >> >> mailing list >> sourceforge fora >> tracker items (bugs and feature requests, both issues and comments) >> wiki changes > > We have a forum? ;) > :) I take this as a sign of support for a unification of the Aperture-related information channels. Antoni Mylka ant...@gm... |
From: Antoni M. <ant...@gm...> - 2008-11-26 12:53:50
|
2008/6/6 Antoni Myłka <ant...@gm...>: > Antoni Myłka pisze: >> >> Christiaan Fluit pisze: >>> >>> Antoni Myłka wrote: >>>> >>>> You are right, we need to integrate: >>>> >>>> mailing list >>>> sourceforge fora >>>> tracker items (bugs and feature requests, both issues and comments) >>>> wiki changes >>> >>> We have a forum? ;) >>> >> >> :) >> >> I take this as a sign of support for a unification of the Aperture-related >> information channels. > > Hello Aperturians! > > I've been quiet for a while but now it's time to go on. The issue raised by > Grant is valid IMHO. There are following information channels: > > those with automatic notifications: (push) > 1. this list > 2. the forum: http://tinyurl.com/3es4e5 ("monitor this forum" link) > 3. 4 different RSS feeds http://tinyurl.com/4ljarj > - wiki updates > - news > - releases > - summary (really cool, includes a download count every day) > > those with no (or partial) notifications (pull) > 1. the trackers: > - bugs: http://tinyurl.com/3qtmlv > - feature requests: http://tinyurl.com/46t7vn > Having real email notifications about all tracker activity requires a > paid sourceforge account (which sucks IMHO). I only get notified > about items submitted by or assigned to me. Does anyone have some > idea? > 2. the svn log: http://tinyurl.com/3okx6f > I can set up a commit mailing list, do you think it's worthwile? > > I have already hidden one unused tracker ("Patches") and two unused forums > ("Developers" and "Help"). The "Open Discussion" has been renamed to > "Aperture Forum". Now it's cleaner. (Two trackers, one forum). > > It is possible (and easy) to set up a commit mailing list. Do you think it's > worthwile? > I resurrect this thread because SF has enabled a timeline functionality at last. Under http://sf.net/projects/aperture there are five tabs: news, details, public, related, activity. Click on Activity and see what's been cooking. All forum posts and tracker comments are there. I'm also setting up a commit mailing list and will add a hook to SVN. This will allow me to get up in the morning, brew myself a coffee and see 1. aperture-dev posts 2. forum posts - email from 'watch this project' 3. wiki updates - rss feed 4. statistics (e.g. the download count), news and releases - rss feed 5. all tracker activity (new and changed issues) - email 6. all commits - email from aperture-commit All in two folders in Thunderbird mails and RSS. Now I won't miss anything anymore. My question is: do you want to have it all channelled to aperture-dev? IMHO it would be a good idea. It's a developer list and we're the Aperture community aren't we? Otherwise everyone interested will have to set it all up by him/herself. -- Antoni Myłka ant...@gm... |
From: Leo S. <leo...@df...> - 2008-11-26 20:40:36
|
It was Antoni Mylka who said at the right time 26.11.2008 13:53 the following words: > 2008/6/6 Antoni Myłka <ant...@gm...>: > >> Antoni Myłka pisze: >> >>> Christiaan Fluit pisze: >>> >>>> Antoni Myłka wrote: >>>> >>>>> You are right, we need to integrate: >>>>> >>>>> mailing list >>>>> sourceforge fora >>>>> tracker items (bugs and feature requests, both issues and comments) >>>>> wiki changes >>>>> >>>> We have a forum? ;) >>>> >>>> >>> :) >>> >>> I take this as a sign of support for a unification of the Aperture-related >>> information channels. >>> >> Hello Aperturians! >> >> I've been quiet for a while but now it's time to go on. The issue raised by >> Grant is valid IMHO. There are following information channels: >> >> those with automatic notifications: (push) >> 1. this list >> 2. the forum: http://tinyurl.com/3es4e5 ("monitor this forum" link) >> 3. 4 different RSS feeds http://tinyurl.com/4ljarj >> - wiki updates >> - news >> - releases >> - summary (really cool, includes a download count every day) >> >> those with no (or partial) notifications (pull) >> 1. the trackers: >> - bugs: http://tinyurl.com/3qtmlv >> - feature requests: http://tinyurl.com/46t7vn >> Having real email notifications about all tracker activity requires a >> paid sourceforge account (which sucks IMHO). I only get notified >> about items submitted by or assigned to me. Does anyone have some >> idea? >> 2. the svn log: http://tinyurl.com/3okx6f >> I can set up a commit mailing list, do you think it's worthwile? >> >> I have already hidden one unused tracker ("Patches") and two unused forums >> ("Developers" and "Help"). The "Open Discussion" has been renamed to >> "Aperture Forum". Now it's cleaner. (Two trackers, one forum). >> >> It is possible (and easy) to set up a commit mailing list. Do you think it's >> worthwile? >> >> > > I resurrect this thread because SF has enabled a timeline functionality at last. > > Under http://sf.net/projects/aperture there are five tabs: news, > details, public, related, activity. Click on Activity and see what's > been cooking. All forum posts and tracker comments are there. I'm also > setting up a commit mailing list and will add a hook to SVN. This will > allow me to get up in the morning, brew myself a coffee and see > > 1. aperture-dev posts > 2. forum posts - email from 'watch this project' > 3. wiki updates - rss feed > 4. statistics (e.g. the download count), news and releases - rss feed > 5. all tracker activity (new and changed issues) - email > 6. all commits - email from aperture-commit > > All in two folders in Thunderbird mails and RSS. Now I won't miss > anything anymore. > > My question is: do you want to have it all channelled to aperture-dev? > IMHO it would be a good idea. It's a developer list and we're the > Aperture community aren't we? Otherwise everyone interested will have > to set it all up by him/herself. > Excellent! In other projects, we made a second mailinglist to make it optional. We oculd make another aperture mailinglist for the updates developers, what do you think? best Leo -- ____________________________________________________ DI Leo Sauermann http://www.dfki.de/~sauermann Deutsches Forschungszentrum fuer Kuenstliche Intelligenz DFKI GmbH Trippstadter Strasse 122 P.O. Box 2080 Fon: +49 631 20575-116 D-67663 Kaiserslautern Fax: +49 631 20575-102 Germany Mail: leo...@df... Geschaeftsfuehrung: Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 ____________________________________________________ |
From: Leo S. <leo...@df...> - 2008-05-19 07:06:53
|
It was Grant Ingersoll who said at the right time 14.05.2008 20:13 the following words: > 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) > Hi, I copied rules from some other project long ago, see here: http://aperture.wiki.sourceforge.net/GettingInvolved which is linked in the main-menu (left) of the wiki. but you mentioned many more ideas about making this better. My personal view on community and the discussion process is: * we tend to over-engineer and I would love to keep the software as simple as possible to achieve the goal we need * it should be very easy to contribute We are open for "slow" changes and adaptions, if you have two or three minor changes to our way of handling things, or to the guidelines that are written on the homepage (aperture.sourceforge.net), -> submit a patch ! (the homepage is in aperture-svn/doc and can be diffed) best Leo > 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. > > Cheers, > Grant > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Aperture-devel mailing list > Ape...@li... > https://lists.sourceforge.net/lists/listinfo/aperture-devel > -- ____________________________________________________ DI Leo Sauermann http://www.dfki.de/~sauermann Deutsches Forschungszentrum fuer Kuenstliche Intelligenz DFKI GmbH Trippstadter Strasse 122 P.O. Box 2080 Fon: +49 631 20575-116 D-67663 Kaiserslautern Fax: +49 631 20575-102 Germany Mail: leo...@df... Geschaeftsfuehrung: Prof.Dr.Dr.h.c.mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Amtsgericht Kaiserslautern, HRB 2313 ____________________________________________________ |
From: Antoni M. <ant...@gm...> - 2008-06-06 18:46:27
|
Antoni Myłka pisze: > Christiaan Fluit pisze: >> Antoni Myłka wrote: >>> You are right, we need to integrate: >>> >>> mailing list >>> sourceforge fora >>> tracker items (bugs and feature requests, both issues and comments) >>> wiki changes >> >> We have a forum? ;) >> > > :) > > I take this as a sign of support for a unification of the > Aperture-related information channels. Hello Aperturians! I've been quiet for a while but now it's time to go on. The issue raised by Grant is valid IMHO. There are following information channels: those with automatic notifications: (push) 1. this list 2. the forum: http://tinyurl.com/3es4e5 ("monitor this forum" link) 3. 4 different RSS feeds http://tinyurl.com/4ljarj - wiki updates - news - releases - summary (really cool, includes a download count every day) those with no (or partial) notifications (pull) 1. the trackers: - bugs: http://tinyurl.com/3qtmlv - feature requests: http://tinyurl.com/46t7vn Having real email notifications about all tracker activity requires a paid sourceforge account (which sucks IMHO). I only get notified about items submitted by or assigned to me. Does anyone have some idea? 2. the svn log: http://tinyurl.com/3okx6f I can set up a commit mailing list, do you think it's worthwile? I have already hidden one unused tracker ("Patches") and two unused forums ("Developers" and "Help"). The "Open Discussion" has been renamed to "Aperture Forum". Now it's cleaner. (Two trackers, one forum). It is possible (and easy) to set up a commit mailing list. Do you think it's worthwile? Antoni Mylka ant...@gm... |