Re: [Geany-devel] POLL started (was: Re: Newsletter: Markuplangauge)
Hi, On Sun, 5 Jun 2011 19:26:16 +0200 Frank Lanitz wrote: > On Wed, 01 Jun 2011 10:54:18 +0200 > Frank Lanitz wrote: > > > Based on that list I will create a poll upcoming weekend (around > > June, 4th) - I will announce tis inside another mail with some > > basic rules. > > I've just started the poll with all options given inside the wiki at > http://wiki.geany.org/newsletter/markuplanguages > > You can join the poll at > http://doodle.com/nnrmb2bakye8m4sz > > Please be so fair and do only do participate, if you really want to > contribute or have any other connection to the newsletter. > > I will close the poll upcoming weekend (11. June) Well, still early in the morning CEST, but I guess the outcome was clear: Currently we do have 6 participants. 5 votes for ReST, 2 for AsciiDoc and one for LaTeX. Beside one which voted for ReST all of the participants don't care much about in addition to its favorite choice. So we do have a decision: issue 3+ will be done in ReST. Next steps (just a few points): Colomban did some nice work on creating the pdf from ReST a couple of days ago. I will merge his changes into master and will start to convert issue 1 and 2 to latest version so newsletter looks the same. Also Russell did start to write some cool content for issue 3 as well as there have been some discussion on linking and putting which content to newsletter/wiki during last days on mailing list. I did not yet set a release date but I guess sometime mid July would be a good idea. Cheers, Frank -- http://frank.uvena.de/en/ pgpewC59qIfoS.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Patch Tracker
On Thu, 09 Jun 2011 19:40:26 +0200 Thomas Martitz wrote: > We made the following observation after years with a patch tracker. If > core developers are rare or lack time or can't otherwise regularly look > at the patches (which is the case for Geany too), [...] Nothing will work in this case. > The problem is that a patch tracker creates the idea that once a patch > is uploaded the project is responsible for them and not the contributor. I wonder how. A serious patch is likely to break on ~100 svn revisions, and you must update it, to be able to use it yourself. > The way I see it is that a patch tracker will not work for Geany. +1. But it's still better than the mailing list. -- E-gards: Jimmy ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Patch Tracker
On 06/10/11 00:01, Thomas Martitz wrote: Additionally, if the contributor is not motivated enough to bring up patches again and again then neither the maling list or patch tracker help. In this case it's simply the contributors fault. Without going into a rant, I will just say that I could not possibly disagree with you more on that point. Cheers, Matthew Brush ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Patch Tracker
> Unless the patch tracker lives long enough to grow to a couple (say 50) > patches in which case patches not clearly represented anymore and it's > de-motivating to even look at the patch tracker, let alone individual > patches. In a voluntary project no-one is *required* to do anything with patches (or anything else for that matter) so, as Thomas says just putting them in a tracker isn't going to have them addressed, but, as Matthew argues at least developers know where to look for them. The developers are interested in adding things they want or see are needed, and occasionally have a fit of conscience and try to apply some patches. Frankly feeling guilty or harrassed is a bad way of keeping developers motivated. If the project is going to say patches welcome (tm) then there should be enough developers who agree to assess and apply patches (more than one to allow for breaks, by choice or forced). That needs people who have time and enough knowledge of Geany's code to put their hands up to Enrico and ask for the ability to do this, for example people who have submitted enough patches and demonstrated enough responsibility for the community to have confidence in them. > >> >> Of course, like you said, if nobody looks at it ever, it's still pretty >> useless. > > Additionally, if the contributor is not motivated enough to bring up patches > again and again then neither the maling list or patch tracker help. In this > case it's simply the contributors fault. Harsh and not terribly welcoming and motivating either, remember that people submitting patches are the projects best source of possible future developers to help spread the workload and thus improve the situation. I'm sure that the current situation isn't deliberate on the part of the developers, just circumstances, Nick is MIA, Enrico has very little time, I have very little time etc. So again what it needs is for more people to volunteer who have shown that they have the experience and responsibility. The more people who each do a little bit the easier it is for all. Cheers Lex ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Patch Tracker
Am 10.06.2011 02:09, schrieb Matthew Brush: On 06/09/11 10:40, Thomas Martitz wrote: Am 27.05.2011 23:31, schrieb Matthew Brush: Hi, Would it be useful for someone with admin rights on SourceForge.net to create a "Patch Tracker"? I've seen some projects with this[1]. We, at Rockbox, are in the process of abandoning our patch tracker. Because it has grown to host over 400 patches, nice ones as well as bad ones, which nobody looks at. We made the following observation after years with a patch tracker. If core developers are rare or lack time or can't otherwise regularly look at the patches (which is the case for Geany too), it will become a place to let patches rot. The problem is that a patch tracker creates the idea that once a patch is uploaded the project is responsible for them and not the contributor. This means the contributor is less motivated to work on the patch to make it committable or to pester developers. The way I see it is that a patch tracker will not work for Geany. So it's better to let them rot in the (non-searchable) archives of a mailing list? No it's not (in our experience anyway), since the possibility of getting lost in the mailing list motivates the contributors to regularly bring up the patches again and remind core developers. This doesn't happen on a patch tracker, but is happening right now on the mailing list. It's at least a bit better than the current situation, since it's easier for a core developer to see a list of outstanding patches in one page, and people down the road can see the patches and update them to work with newer versions later if they get forgotten. Unless the patch tracker lives long enough to grow to a couple (say 50) patches in which case patches not clearly represented anymore and it's de-motivating to even look at the patch tracker, let alone individual patches. Of course, like you said, if nobody looks at it ever, it's still pretty useless. Additionally, if the contributor is not motivated enough to bring up patches again and again then neither the maling list or patch tracker help. In this case it's simply the contributors fault. Best regards. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
