Dear Pytrainer developers, I have kind of been lurking on the list and on Trac and I would like to use this opportunity to introduce myself and discuss a contribution I could possibly make to the project.
Firstly, I am a daily user of Pytainer (my unconventional usage will be clarified below) and I have submitted a few bug reports (and proposed solutions) in the past. My congratulations to the project team for a great Python application and for the well structured and well commented code. Specifically, I use Pytrainer to record and visualize my cardio-vascular and weight training. For these purposes I have added code to my personal copy of 1.8.0. as follows: 1. Added an 'Activity Types' tab to the preferences dialog where I can create categories of 'Sports', e.g. 'Weights', 'Cardio-Vascular', etc 2. Created different PyGTK (Glade) interfaces for each 'Activity Type' e.g. M.E.T. makes sense for cardio, but for weights the Add/Edit Sports dialog asks for R.M. (repetition maximum). 3. To implement the above I have had to add MySQL tables and a few additional fields to existing tables. That's it. I have not extended the additional functionality to category specific graphs and calculators yet, but this is my intention. So, is the development team keen on implementing this additional functionality in a future version of Pytrainer? If yes, what can I do to progress the matter? If no, would there be any objection to a project fork (with a related name)? I would prefer the first option, but will respect the voice of democracy (or the BDFL). regards, Werner van Staden On Sat, 2011-07-16 at 13:23 +0200, David García Granda wrote: > Hi, > > > There's three issues regarding the version number I want to discuss. > > Let's see. > > > The first is simply that it should now be changed from 1.8.1 to 1.9.0 > > because a new feature has been added since 1.8.0 was released. > > Right. > > > Secondly, the current version number in source code and the current > > version number in the bug tracker do not match. This should never > > happen - as soon as 1.8.0 was released the version number of trunk > > should have been bumped up to 1.8.1. I think we should have a > > formalised release procedure which documents things like this. > > Although I agree, to be honest there is not so many people > contributing to pytrainer and therefore I don't expect tickets but > current distribution list regarding development version issues so I am > not really worried about. > > > Thirdly, that the version number is defined in main.py and manually > > includes the VC revision number means main.py is modified in every > > other commit. This makes browsing the main.py revision log extremely > > difficult - > > I agree. > > > it made my job of searching for historical schema changes > > harder than it needed to be. In the long term we should move the > > version number to its own file. In the short term I would like to put > > a halt to the convention of including the SVN revision number in the > > trunk version number. Instead of "-svn#<rev>" I suggest we just use > > "-dev" as the suffix for the development trunk. This will dramatically > > reduce the number of commits made against main.py. > > I like the idea even more if we can automatize it. > > The reason for including revision number was to make clearer which > development version is running when making changes as it appears in > title bar. > > I agree we need to automatize release process but keep in mind that we > don't have an stable number of contributors and we depend on each > one's spare time and effort to make things move. > > When releasing a version next one is automatically set to higher minor > release. But then someone pops up with a new feature, sends a > contribution via email (I have a couple of them still in my to-do list > O:)) or files a bug and although I am aware is not the best practice, > I am not personally in the mood to start creating branches that need > to be merged afterwords. > > Regards, > > David > > ------------------------------------------------------------------------------ > AppSumo Presents a FREE Video for the SourceForge Community by Eric > Ries, the creator of the Lean Startup Methodology on "Lean Startup > Secrets Revealed." This video shows you how to validate your ideas, > optimize your ideas and identify your business strategy. > http://p.sf.net/sfu/appsumosfdev2dev > _______________________________________________ > Pytrainer-devel mailing list > Pytrainer-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/pytrainer-devel ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Pytrainer-devel mailing list Pytrainer-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pytrainer-devel
