After having spent a week lurking on the wxWidgets dev-list I have changed
my opinion on one of these; see below ...
--Ed
> -----Original Message-----
> From: Martyn Shaw [mailto:martynshaw99@...]
> Sent: Sunday, November 01, 2009 3:12 PM
> To: audacity-devel@...
> Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback
>
>
>
> Ed Musgrove wrote:
> > I think what you said is pretty much what I said:
> > "enhancement" == "feature request"
> > "a developer" == " venerable Audacity mentor"
> > " (or more loosely, active contributors to this list)" == "hackers
> > (like me)"
> > To get from
> > http://wiki.audacityteam.org/index.php?title=Feature_Requests
> > to a "formal enhancement" requires intervention by an Audacity PTB.
> >
> > As for storing non-committed patches, I do not think it a good idea.
>
> They should be kept somewhere, in case we want to look at them.
>
[ Ed-- ]
The folks developing wxWidgets are using a patch tracker, here is an
example:
http://trac.wxwidgets.org/ticket/11372#comment:3
Which is based on an open-source project, Trac:
http://trac.wxwidgets.org/about
> Any
> > patch proposed by ANYONE active on the dev-list should be first
> > attached (zipped if large) to a dev-list message. This leaves it open
> > for peer review and automatically stores it online at Source Forge
> > (though the interface is not good for locating old attachments).
>
> That is part of the problem, yes.
>
> Those not on the dev-list should
> > attach a (zipped--neither .patch nor .txt files are allowed) file to a
> > post on http://wiki.audacityteam.org/index.php?title=Feature_Requests.
>
> That would be a good idea. How does that work? I am not very good
editing
> wikis.
>
[ Ed-- ]
No editing of a wiki is involved. This is just a forum (bulletin board) with
a fairly good interface. The messages are threaded, one may subscribe to a
message (get e-mail notification when a message gets a new reply), insert
hyperlinks in your messages (this allows you to embed pictures in your post
which you have stored elsewhere) and attach files (zipped) which other
readers may easily download.
> Martyn
>
> > --Ed
> >
> >
> >> -----Original Message-----
> >> From: Gale Andrews [mailto:gale@...]
> >> Sent: Saturday, October 31, 2009 1:18 PM
> >> To: audacity-devel@...
> >> Subject: Re: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback
> >>
> >>
> >> | From "Ed Musgrove" <edgarmusgrove@...> Fri, 30 Oct
> 2009
> >> | 21:54:03 -0700
> >> | Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback
> >>> Is Audacity a professionally developed product? Is it just something
> >>> that a few people have thrown together in their spare time? Do we
> >>> expect Audacity to be used primarily by those capable of compiling
> >>> and understanding the source code, or are the vast majority of users
> >>> audiophiles who have no desire nor ability to compile the code? Can
> >>> the venerable Audacity mentors who are more focused on major
> >>> problems accept the enthusiast coder who might be more comfortable
> >>> starting out
> >> dealing with the little things?
> >>> Any change in the code should be documented. If it is a trivial
> >>> change made by a longtime developer a comment with initials and the
> >>> date next to the change might be sufficient. Anything which changes
> >>> the user's experience should be formally proposed, discussed and the
> >>> code peer-reviewed with alpha testing by at least one developer on
> >>> each major
> >> platform.
> >>> I think we need a category of bug like "feature request". That way
> >>> something sent to @feedback can be triaged by venerable developers
> >>> into this category when appropriate. Recognized developers and
> >>> hackers (like me) may also propose a "feature request" bug; someone
> >>> with authorization on the bug list would need to actually enter it.
> >> We've pretty much agreed as far as I understand it that "enhancements"
> >> tracked in Bugzilla or whatever system we use should only be those
> >> supported by a developer (or more loosely, active contributors to
> >> this
> > list).
> >> User requests sent to feedback@ will continue to be processed on:
> >> http://wiki.audacityteam.org/index.php?title=Feature_Requests
> >>
> >> We can take valuable/strongly voted for items from that page at any
> >> time and turn it into a "developer supported" enhancement.
> >>
> >> The point of my question was whether we want to load a formal bug
> >> tracker with what may be relatively trivial "enhancement" patches by
> >> creating a
> > new
> >> item just to hold that patch; or store patches (or links to
> >> them) otherwise.
> >>
> >> Obviously if we use Bugzilla we can attach a patch to an actual P1-
> >> P5 bug
> > (or
> >> if Checklist remains in the short/medium term, a link to the patch).
> >> A
> > patch
> >> like that isn't likely to drop out of sight.
> >>
> >> I think the problem is more the large number of patches for
> >> "enhancements", some of which may come from someone completely
> new to
> >> the list, so they couldn't be described as "developer supported" in
> >> the sense of the enhancements I was thinking of storing in the bug
> >> tracker (where the case for them has already been largely agreed).
> >>
> >>
> >>
> >> Gale
> >>
> >>
> >>
> >>>> -----Original Message-----
> >>>> From: Gale Andrews [mailto:gale@...]
> >>>> Sent: Friday, October 30, 2009 9:14 PM
> >>>> To: audacity-devel@...
> >>>> Subject: [Audacity-devel] Patch Tracker WAS Re: Beta_Feedback
> >>>>
> >>>>
> >>>> | From Martyn Shaw <martynshaw99@...> Sat, 31 Oct
> 2009
> >>>> | 00:39:14 +0000
> >>>> | Subject: [Audacity-devel] Beta_Feedback
> >>>>> ... I see no reason (on my platform), or any philosophical reason
> >>>>> why the 'about' box shouldn't be resizable, and so I committed it
> >>>>> (others may chose to revert).
> >>>>>
> >>>>> Just the sort of patch that is distracting us (me) from 2.0. It
> >>>>> should have gone into a patch-tracker of some sort, commented on
> >>>>> by people who tried it but maybe aren't 'committers', and not come
> >>>>> up on -devel until later. This isn't a criticism of you or what
> >>>>> you've done, but of the limited system that we have right now.
> >>>>> I'm hoping that Bugzilla and it's protocols may help with this
> >>>>> type of developer-bandwidth problem.
> >>>> Bugzilla does not from my admittedly limited knowledge have a patch
> >>>> tracker. It has a patch viewer (view patches that you have attached
> >>>> to
> >>> bugs):
> >>>> http://www.bugzilla.org/docs/2.18/html/patchviewer.html
> >>>>
> >>>> So as far as I can see from the test pages we've had so far, that
> >>>> means creating a "bug" or some other "object" for the patch, with
> >>>> cases where
> >>> the
> >>>> patch actually relates to an already listed bug, and cases where
> >>>> the
> >>> object
> >>>> would have to be created specifically for it (as in the above case).
> >>>>
> >>>> If we finally use Bugzilla, is the above a good idea, or are
> >>>> entries on a
> >>> Wiki
> >>>> page better? Those would presumably require the submitter to
> >>>> actually post a short initial message to -devel (patch attached,
> >>>> details of what it does
> >>> on
> >>>> the Wiki).
> >>>>
> >>>> But maybe protocol would require a short message to -devel anyway,
> >>>> even in the case of a "patch tracker"?
> >>>>
> >>>> Comments?
> >>>>
> >>>>
> >>>>
> >>>> Gale
> >>>>
> >>>>
> >>>>
> >>>>> Ed Musgrove wrote:
> >>>>>> After release of "stable" I propose to make the prefs panel user
> >>>>>> resizable (restrained only by valid screen size) and the keyboard
> >>>>>> panel columns automatically size themselves (I have the code
> >>>>>> completely finished) just like the mouse prefs panel is.
> >>>>>> This will resolve most if not all such issues. Vaguely related, I
> >>>>>> gave Gale working code which makes the Help/About... panel user
> >>>>>> resizable. (it is a trivial one line change). BTW, is there a
> >>>>>> problem or reason why
> >>> that
> >>>> was never committed (patch attached)?
> >>>>>> --Ed
> >>>>>>
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: Gale Andrews [mailto:gale@...]
> >>>>>>> Sent: Sunday, October 25, 2009 7:53 PM
> >>>>>>> To: audacity-devel@...
> >>>>>>> Subject: Re: [Audacity-devel] Beta_Feedback
> >>>>>>>
> >>>>>>>
> >>>>>>> | From "Ed Musgrove" <edgarmusgrove@...> To
> >>>>>>> | <audacity-devel@...>
> >>>>>>> | Subject [Audacity-devel] Beta_Feedback
> >>>>>>>> Is it possible that the recent commit to fr.po caused this:
> >>>>>>>>
> >>>>>>>> Update of /cvsroot/audacity/htdocs/locale In directory
> >>>>>>>> 23jxhf1.ch3.sourceforge.com:/tmp/cvs-serv7665
> >>>>>>>>
> >>>>>>>> Modified Files:
> >>>>>>>> fr.po
> >>>>>>>> Log Message:
> >>>>>>>> Updated web site translation from Olivier Humbert
> >>>>>>> No, that is the translation for the web site, not the .po file
> >>>>>>> for the
> >>>>>> software.
> >>>>>>> See below.
> >>>>>>>
> >>>>>>>
> >>>>>>> | From "Ed Musgrove" <edgarmusgrove@...> Sun, 25
> >> Oct
> >>>> 2009
> >>>>>>> | 09:52:08 -0700
> >>>>>>> | Subject: [Audacity-devel] Beta_Feedback
> >>>>>>>> Note that the problem is with width. Note that the Audacity
> >>>>>>>> "system informations" is printed in French.
> >>>>>>>>
> >>>>>>>> I carefully went through both (after having just downloaded the
> >>>>>>>> current
> >>>>>>> CVS
> >>>>>>>> head):
> >>>>>>>> audacity\src\prefs\PrefsDialog.cpp
> >>>>>>>> audacity\src\prefs\KeyConfigPrefs.cpp
> >>>>>>>> To ensure that none of the things I have played with recently
> >>>>>>>> were inadvertently committed -- they were not.
> >>>>>>>>
> >>>>>>>> Recently Gale made some changes to the text. I think that this
> >>>>>>>> dialogue initially sizes itself based on the width of the
> >>>>>>>> longest text string;
> >>>>>> could
> >>>>>>>> this be a translation issue?
> >>>>>>> If the problem is specific to running Audacity in French, using
> >>>>>>> the .mo file compiled from fr.po, then no, because my string
> >>>>>>> changes have not yet had a French translation committed.
> >>>>>>>
> >>>>>>> Using a Unicode Release build from CVS a few days ago on Ubuntu
> >>>>>>> 9.04 (so using the current fr.po file) the longer text seems to
> >>>>>>> wrap round correctly. The preferences dialogue could in fact
> >>>>>>> still be expanded a little horizontally to the full 800px width.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> If possible, I would like to have the reporter comment out that
> >>>>>>>> line so
> >>>>>> that
> >>>>>>>> the dialog will open without entering the debugger, then, send
> >>>>>>>> me a screenshot of the mouse panel, key binding panel and the
> >>>>>>>> directories
> >>>>>>> panel.
> >>>>>>>> Je parle un peut de Francais. (But my spelling and grammar are
> >>>>>> atrocious.)
> >>>>>>> Ed, I've sent you the e-mail address of the person privately, so
> >>>>>>> feel free
> >>>>>> to
> >>>>>>> contact them off-list for more information (but don't overdo it
> >>>>>>> if he isn't keen to go to a lot of trouble). :=)
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Gale
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>> -----Original Message-----
> >>>>>>>>> From: Gale Andrews [mailto:gale@...]
> >>>>>>>>> Sent: Sunday, October 25, 2009 1:28 AM
> >>>>>>>>> To: Laurent Epinat
> >>>>>>>>> Cc: audacity-devel@...;
> >>>>>>>>> feedback@...
> >>>>>>>>> Subject: Re: [Audacity-devel] Beta_Feedback
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Thank you, I have forwarded this message to our developers'
> >>>>>>>>> mailing list.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Gale
> >>>>>>>>> Audacity Team
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> | From Laurent Epinat
> >>>>>>>>> | Sat, 24 Oct 2009 10:34:26 +0200
> >>>>>>>>> | Subject: Beta_Feedback
> >>>>>>>>>> Just for information, I recompile the beta 1.3.9 version on
> >>>>>>>>>> AMD64
> >>>>>>>>>>
> >>>>>>>>>> and I have an assert when I open the preference dialog box at
> >>>>>>>>>> the src/prefs/PrefsDialog.cpp line 136 :
> >>>>>>>>>> wxASSERT_MSG(sz.x <= 800 && sz.y <= 600, wxT("Preferences
> >>>> dialog
> >>>>>>>>>> exceeds max size"));
> >>>>>>>>>>
> >>>>>>>>>> I add trace on the size and my dialog had
> >>>>>>>>>> sz.x=857 sz.y=382
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> My screen resolution is 1920x1200 I you need more information
> >>>>>>>>>> ...
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Congratulation for the really good software
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Here the system informations
> >>>>>>>>>>
> >>>>>>>>>> Informations système
> >>>>>>>>>> Support de format de fichier
> >>>>>>>>>> libmad (Importation de MP3) Activé
> >>>>>>>>>> libvorbis (Import et Export Ogg Vorbis ) Activé
> >>>>>>>>>> libid3tag (support des tag ID3) Activé
> >>>>>>>>>> libflac (Import et Export FLAC) Activé
> >>>>>>>>>> libtwolame (export MP2) Désactivé
> >>>>>>>>>> QuickTime (Importer depuis QuickTime) Désactivé
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Librairies
> >>>>>>>>>> libresample
> >>>>>>>>>> (Conversion de fréquence d'échantillonnage) Activé PortAudio
> >>>>>> (Lecture
> >>>>>>>>>> et enregistrement audio)
> >>>>>>>>>> v19
> >>>>>>>>>> wxWidgets 2.8.10
> >>>>>>>>>> (Unicode)
> >>>>>>>>>>
> >>>>>>>>>> Fonctions
> >>>>>>>>>> Nyquist (Support de modules (plugins))
> >>> Activé
> >>>>>>>>>> LADSPA (Support de modules (plugins))
> >>> Activé
> >>>>>>>>>> Vamp (Support de modules (plugins))
> > Activé
> >>>>>>>>>> Audio Units (Support de modules (plugins))
> >> Désactivé
> >>>>>>>>>> PortMixer (Support du mixage de la carte son) Activé
> >>>>>>>>>> SoundTouch (Support du changement de hauteur et de
> >> tempo)
> >>>>>>>>> Désactivé
> >>>>>>>>>> Informations système
> >>>>>>>>>> Date de création du programme : Oct 18 2009
> >>>>>>>>>> Type de version : Debug build
> >>>>>>>>>> Préfixe d'intallation /usr/local/
> >>>>>>>>>> Répertoire des réglages : /home/laurent/.audacity-data
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>> ----------------------------------------------------------------
> >>>>>> ----
> >>>>>> --------
> >>>>>> --
> >>>>>>> Come build with us! The BlackBerry(R) Developer Conference in
> >>>>>>> SF, CA is the only developer event you need to attend this year.
> >>>>>>> Jumpstart your developing skills, take BlackBerry mobile
> >>>>>>> applications to market and stay ahead of the curve. Join us from
> >>>> November 9 - 12, 2009. Register now!
> >>>>>>> http://p.sf.net/sfu/devconference
> >>>>>>> _______________________________________________
> >>>>>>> audacity-devel mailing list
> >>>>>>> audacity-devel@...
> >>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------
> >>>>>>> ----
> >>>>>>> -----
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------
> >>>>>>> ----
> >>>>>>> ----------- Come build with us! The BlackBerry(R) Developer
> >>>>>>> Conference in SF, CA is the only developer event you need to
> >>>>>>> attend this year. Jumpstart your developing skills, take
> >>>>>>> BlackBerry mobile applications to market and stay ahead of the
> >>>>>>> curve. Join us from November 9 - 12, 2009. Register now!
> >>>>>>> http://p.sf.net/sfu/devconference
> >>>>>>>
> >>>>>>> ---------------------------------------------------------------
> >>>>>>> ----
> >>>>>>> -----
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> audacity-devel mailing list
> >>>>>>> audacity-devel@...
> >>>>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>>>> ------------------------------------------------------------------
> >>>>> ----
> >>>>> -------- Come build with us! The BlackBerry(R) Developer
> >>>>> Conference in SF, CA is the only developer event you need to
> >>>>> attend
> >> this year.
> >>>>> Jumpstart your developing skills, take BlackBerry mobile
> >>>>> applications to market and stay ahead of the curve. Join us from
> >>>>> November 9 - 12, 2009. Register now!
> >>>>> http://p.sf.net/sfu/devconference
> >>>>> _______________________________________________
> >>>>> audacity-devel mailing list
> >>>>> audacity-devel@...
> >>>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>>>
> >>>>
> >>>>
> >>> --------------------------------------------------------------------
> >>> --
> >>> ------
> >>> --
> >>>> Come build with us! The BlackBerry(R) Developer Conference in SF,
> >>>> CA is
> >>> the
> >>>> only developer event you need to attend this year. Jumpstart your
> >>>> developing skills, take BlackBerry mobile applications to market
> >>>> and stay ahead of the curve. Join us from November 9 - 12, 2009.
> >>>> Register
> >> now!
> >>>> http://p.sf.net/sfu/devconference
> >>>> _______________________________________________
> >>>> audacity-devel mailing list
> >>>> audacity-devel@...
> >>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>>
> >>> --------------------------------------------------------------------
> >>> --
> >>> -------- Come build with us! The BlackBerry(R) Developer Conference
> >>> in SF, CA is the only developer event you need to attend this year.
> >>> Jumpstart your developing skills, take BlackBerry mobile
> >>> applications to market and stay ahead of the curve. Join us from
> >>> November 9 - 12, 2009. Register now!
> >>> http://p.sf.net/sfu/devconference
> >>> _______________________________________________
> >>> audacity-devel mailing list
> >>> audacity-devel@...
> >>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >>
> >>
> >>
> > ----------------------------------------------------------------------
> > ------
> > --
> >> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> >> is
> > the
> >> only developer event you need to attend this year. Jumpstart your
> >> developing skills, take BlackBerry mobile applications to market and
> >> stay ahead of the curve. Join us from November 9 - 12, 2009. Register
> now!
> >> http://p.sf.net/sfu/devconference
> >> _______________________________________________
> >> audacity-devel mailing list
> >> audacity-devel@...
> >> https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >
> >
> > ----------------------------------------------------------------------
> > -------- Come build with us! The BlackBerry(R) Developer Conference in
> > SF, CA is the only developer event you need to attend this year.
> > Jumpstart your developing skills, take BlackBerry mobile applications
> > to market and stay ahead of the curve. Join us from November 9 - 12,
> > 2009. Register now!
> > http://p.sf.net/sfu/devconference
> > _______________________________________________
> > audacity-devel mailing list
> > audacity-devel@...
> > https://lists.sourceforge.net/lists/listinfo/audacity-devel
> >
>
>
----------------------------------------------------------------------------
--
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA is
the
> only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> audacity-devel mailing list
> audacity-devel@...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
|
