Hey Nick. The best way is to open new JIRA as the way to discuss and track the feature. JIRA can have a number of sub-tasks if needed and each subtask can be committed separately in case the feature would allow for an incremental development.
If increments won't do for one reason or another then the development would need to be done on a branch and it certainly would require an involvement from a bigger community, so that one day we won't need to review a big-ass patch. At any rate a JIRA would be a good way to start even if for design/proposal discussions. -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing. On Sat, Oct 27, 2012 at 10:21PM, Nick Kolegraff wrote: > Hello BigTopers! > > I'm brand new to the project but have had my eye on it for sometime, also > spoke with Bruno and Roman about some of the things I'm working on. Looking > forward to engaging with the community. > > I'd like to merge my work on www.datasciencelinux.com to the BigTop > Community. However, I'd like to get input from the group on the best way > to go about this. Currently, it is a bare bones system fully stripped of > un-needed packages + a slightly optimal kernel configuration for CPU/IO > intensive things (really just me flicking some switches). I'd like to > explore adding a feature to BigTop that would allow users to build > a minimal system for running the hadoop ecosystem. Really, something like > 'make scratch' that runs a series of targets that build a self contained > system from source. But, that would be quite the patch if I came back in 3 > months and said Hey! Merge me! I'm wondering if there is an incremental > way to do this that would be beneficial to the project? Or should I just > expect to maintain my own fork for such a request? > > Cheers! > Nick
signature.asc
Description: Digital signature
