Hi! El mar, 23-10-2012 a las 09:25 -0400, Dave Brondsema escribió: > On 10/5/12 8:42 AM, Alvaro del Castillo wrote: > > Hi all! > > > > El mié, 11-07-2012 a las 10:07 +0200, Alvaro del Castillo escribió: > >> Hi guys, > ... > >> It is just a first try of the technology and possibilities. And now it > >> is time to define next steps, cleanup code and work with Allura > >> community in order to decide the best way to implement things. > >> > >> The source code for the module is in: > >> > >> https://github.com/Bitergia/AlluraBitergiaMetrics > > > > > > We have moved the code to Sourceforge and works in a fork from git > > Allura. We have sent a "merge request" to Allura project in order you > > can see exactly the code of the module. > > > > https://sourceforge.net/p/allura/git/merge-requests/8/ > > > > Our plan is to continue from now working in this Allura git for inside > > Sourceforge in order to do "merge request" as development goes on. > > > > First off, as I mentioned in my email about the user profile/skills merge > request, I hope we can provide better feedback faster and not leave such big > contributions hanging like this :/
Great! > > I think my basic question here is what tools should go in the main Allura > repo? > Very open ended question for anyone in this new community to voice their > opinion on. > > The current Allura repo has Blog, Discussion, Git, Hg, SVN, Link, Tracker, and > Wiki. It also has some "beta" tools like Activity, Chat and ShortUrl. The Hg > tool we've already discussed moving to a separate repo due to GPL licensing. > SourceForge has some internal tools in a separate repo, and we have a Pastebin > tool open source but completely separate from Allura at > https://sourceforge.net/p/forgepastebin/code/ > > One of the great advantages of the Allura tool system is that they are very > pluggable. An allura sysadmin can deploy whichever included tools and > "external" tools they want. Yes, and from a developer point of view, it is very flexible to create new modules and develop them independently, as AlluraBitergiaMetrics. > > We can talk about both this AlluraBitergiaMetrics tool and tools in general. > I > am currently thinking that AlluraBitergiaMetrics might be good to keep as a > separate tool and not merge it into the core yet, since there is cleanup to > do. Yes, the point is in which moment a module is mature enough to enter into the Allura repo. Thinking in Allura as a platform, I am now inspired by GNOME, we will have the Allura Platform with official modules, and a lot of different modules a part from that. For example, I was thinking about the module name. The short is "Metrics" but I think this name should be for the official Allura Platform Metrics module. I hope in the next weeks/months Bitergia module could be this one, but currently, it is a bit soon to decide it. > Then we don't have to keep merging your new changes in as you develop, you > can > just move forward directly. I also think it might be good for us to move some > of our "beta quality" tools like Activity and Chat and ShortUrl out of > Allura's > main repo and into standalone repos like Pastebin is. > > What are other peoples' thoughts? > > > P.S. I noticed > AlluraBitergiaMetrics/bitergiametrics/nf/metrics/VizGrimoireJS/src/Commits.js > has a GPL license Yes, but we can change that if needed. In spirit our work normally is GPL, but we are not closed to change the license to a more liberal one like ASL 2. Thank you Dave for opening this discussion. Cheers > > > -- |\_____/| Alvaro del Castillo [o] [o] [email protected] - CTO, Software Engineer | V | http://www.bitergia.com | | -ooo-ooo- |\_____/| Alvaro del Castillo [o] [o] [email protected] - CTO, Software Engineer | V | http://www.bitergia.com | | -ooo-ooo-
