On Sat, May 21, 2011 at 14:30, Marc-André Moreau <[email protected]> wrote: >> At work I use Remine for managing our issues and like ... I am curious >> to know what JIRA would give you that GitHub issue tracking wouldn't? > > Project management, such as assigning estimates to tasks, putting tasks in a > product backlog, taking tasks from the product backlog to put them in an > iteration backlog, generating burn down charts for an iteration, calculating > team velocity, etc
Except for estimates (that I really don't see a use for a project of our size) those can be done from git shortlog as is done by many big projects as Linux, OpenEmbedded, Xorg and so on. > did you mean Redmine, and not Remine? Yes; mistyped it. > Those project management features are most likely needed for coordinating > employees for which you know how much time has been allocated for them. This is outside of FreeRDP focus I think. > Also, if you've never used scrum (or an agile process), my argumentation > will probably not make sense to you. Issue tracking like what we have on > github is probably good enough for the community at large, but as we get > more companies involved with paid employees, I think they'll need a real > project management tool. Those need to be done inside of the company IMO and we can rethink it when we GET those. Up to there it will be waste of time and confusing for all of us. >> For grouping issues (be it a subproject or a version) milestones could >> be used. We have wiki on GH ... so what is missing? > > For the community at large, I think that what we have on github is good > enough. However, I think it's good to have a real project management system > set up as the need for it will become more important as time goes. What I see is not handled tasks, for example the issue #17 (IIRC) that Eduardo pushed and I closed yestarday. It was open with a ready and well written patch since begin of April and noone commited it. More issues can be there without being fixed or handled due lack of people looking at them. I also valuate a lot the easy tracking of pull request and how it can be done to comment about issues on the code. It is quite clear for anyone looking at it what is missing and what is being done. This is not done on JIRA. One example of its usage is our Smartcard pull request where we did it and worked well. For FreeRDP it seems much more important to handle issues and pull requests then emploee time. The last IMO is company responsability and putting an infra-structure for it seems overdesigning IMO. Linux and other big projects that has a lot of people and companies working with them do not have this and this wasn't a reason to companies to not work with them. The focos of the projects is result not management of resources and this is companies reponsability. We need a way to handle what is being done and what is missing to be done. Issues work fine for it. We don't need charts and like. I seriously think we need to better handle the amount of open issues we have. JIRA is confusing for me and I didn't see a easy way to find out what is need to be done and who is working on what. GitHub is well suited for it since it is quite near of the source code and able to be integrated with it. Maybe it is me that dislikes the JIRA interface but if it is the case we ought to rethink where we will handle issues and choose ONE place. Be it JIRA or GitHub. Two seems overkill. -- Otavio Salvador O.S. Systems E-mail: [email protected] http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ Freerdp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freerdp-devel
