[onap-tsc] Updated TSC Charter
ubcommunitee with a new set of committers (or likely to be). > In my mind, its much easier in a multi-repo environment to miss the "Hey, > that's actually different committers involved and should probably be a new > project" mark. > 2) Repo splits have costs both way. Multiple repos make it harder for folks > to check out all the code, but easier to grab just one corner of it. > Multiple repos make builds more complex, but faster. > e > > My past experience has been that TSCs are at their best when they ask > projects to *consider* questions, express that they have thought about them, > but then defer broadly to the guys on the ground (a projects committers). > > Do you have thoughts for how that might be done in this situation? > > Ed > > > So in my mind this will either lead to: > > A.) unnecessary red tape overhead > B.) people combining things into a single repo because they don?t want to do > the red tape. > > (and believe me I know red tape ?.). Probably you get a bit of both. > > > Oliver > > > On Apr 21, 2017, at 12:07 PM EDT, Ed Warnicke > gmail.com<mailto:hagbard at gmail.com>> wrote: > > > > Oliver, > > > > For my edification, can you give an example or two of where a well scoped > > project would set up multiple repos? > > > > Ed > > > > On Fri, Apr 21, 2017 at 8:47 AM, SPATSCHECK, OLIVER (OLIVER) > research.att.com<mailto:spatsch at research.att.com>> wrote: > > I have another question on the charter. I just noticed that a project (or > > sub project) and a repo are the same thing. I find this to be sub optimal. > > In my mind a project is a well defined scope of work. A repo has to do with > > how to optimize my code management. Am I the only one with the concern > > that binding the two will force people into sub optimal repo structures? > > > > Thx > > > > Oliver > > ___ > > ONAP-TSC mailing list > > ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> > > https://lists.onap.org/mailman/listinfo/onap-tsc > > > > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/08879d09/attachment-0001.html>
[onap-tsc] Updated Invitation: ONAP Project: TSC Meeting @ Thu Apr 27, 2017 07:00 - 08:00 (PDT) (onap-tsc@lists.onap.org)
This event has been changed. Title: ONAP Project: TSC Meeting Agenda: June Face 2 Face Future Meetings / Times Continue the discussion of the TSC Charter. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/993784494 Or iPhone one-tap (US Toll): +16465588656,993784494# or +14086380968,993784494# Or Telephone: Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll) Meeting ID: 993 784 494 International numbers available: https://zoom.us/zoomconference?m=yQj50mhKQjWwg_Y0RaZ4mxBaHW96doM3 (changed) When: Thu Apr 27, 2017 07:00 ? 08:00 Pacific Time (changed) Where: https://zoom.us/j/993784494 Calendar: onap-tsc at lists.onap.org Who: * Casey Cain - organizer * robert.pippert at ril.com * arthur at gigaspacees.com * Philip Robb * aayush.bhatnagar at ril.com * amir at gigaspaces.com * dp00476350 at techmahindra.com * grace.lian at intel.com * onap-tsc at lists.onap.org Event details: https://www.google.com/calendar/event?action=VIEW=ZHU3ZnZtNG12cGVrcm5tY3ZkNDN2cG9pMGsgb25hcC10c2NAbGlzdHMub25hcC5vcmc=MjUjY2NhaW5AbGludXhmb3VuZGF0aW9uLm9yZzljNzRlYjk4N2RkMDc4OWM4ODVmMmUyODhlZTZmY2FiMDdiMWFhMTA=America/Los_Angeles=en Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account onap-tsc at lists.onap.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -- next part -- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/36e33a7a/attachment.html> -- next part -- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2638 bytes Desc: not available URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/36e33a7a/attachment.ics> -- next part -- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2689 bytes Desc: not available URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/36e33a7a/attachment.bin>
[onap-tsc] Invitation: ONAP Project: TSC Meeting @ Fri Apr 21, 2017 07:00 - 08:00 (PDT) (onap-tsc@lists.onap.org)
You have been invited to the following event. Title: ONAP Project: TSC Meeting Hi there, Casey Cain is inviting you to a scheduled Zoom meeting. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/993784494 Or iPhone one-tap (US Toll): +16465588656,993784494# or +14086380968,993784494# Or Telephone: Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll) Meeting ID: 993 784 494 International numbers available: https://zoom.us/zoomconference?m=yQj50mhKQjWwg_Y0RaZ4mxBaHW96doM3 When: Fri Apr 21, 2017 07:00 ? 08:00 Pacific Time Where: https://zoom.us/j/993784494 Calendar: onap-tsc at lists.onap.org Who: * Casey Cain - organizer * robert.pippert at ril.com * arthur at gigaspacees.com * Philip Robb * aayush.bhatnagar at ril.com * amir at gigaspaces.com * dp00476350 at techmahindra.com * grace.lian at intel.com * onap-tsc at lists.onap.org Event details: https://www.google.com/calendar/event?action=VIEW=ZHU3ZnZtNG12cGVrcm5tY3ZkNDN2cG9pMGsgb25hcC10c2NAbGlzdHMub25hcC5vcmc=MjUjY2NhaW5AbGludXhmb3VuZGF0aW9uLm9yZzljNzRlYjk4N2RkMDc4OWM4ODVmMmUyODhlZTZmY2FiMDdiMWFhMTA=America/Los_Angeles=en Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account onap-tsc at lists.onap.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding -- next part -- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/e51c98a0/attachment-0001.html> -- next part -- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2612 bytes Desc: not available URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/e51c98a0/attachment-0001.ics> -- next part -- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2662 bytes Desc: not available URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/e51c98a0/attachment-0001.bin>
[onap-tsc] Updated TSC Charter
I think one option would be to stick with the project approval as outline but allow multiple repos in one project as decided by the project team. Then we could have a repo coordinator who provides advice to the projects on repos and races issues (like this should really be two projects) to the TSC as they occur which allows the TSC to intervene (e.g. splitting the project). Similarly to your philosophy I believe into trusting the people which do the work and dealing with problems IF they happen rather then trying to design a process which is heavy handed trying to address anticipated issues which might rarely/never occur. Oliver > On Apr 21, 2017, at 1:47 PM EDT, Ed Warnicke wrote: > > Inline... > > On Fri, Apr 21, 2017 at 9:22 AM, SPATSCHECK, OLIVER (OLIVER) research.att.com> wrote: > > I guess you could argue that our current code base is not well formed but if > you look at Gerrit right now you see about 60+ repos for the couple of > components we have. > > LOL... I try not to argue that somebody elses work is not well formed till I > can understand a bit better both their constraints and reasoning ;) > But when they do things that don't make immediate sense to me... I *do* get > curious and want to understand :) > So about the worst you are going to get from me is that seeking to understand > and perhaps some "Have you thought of this" questions :) > > > Let?s just start with A. A in my mind is one project. The scope of the > project is to provide a current inventory for ONAP. > > It consist of 5 repos. > > - AAI Chef cookbooks > - AAI Chef environment files > - AAI REST based services > - AAI common logging library > - Loads SDC Models into A > > now could we have thrown all of this into one repo? Sure we could have but I > think they are functionally separate enough that they shouldn?t be in the > same repo so they can be managed separately (e.g. versioning, patches, > releases etc?). Also not every ONAP user might use all of them (e.g. somebody > might not want to use chef and add an ansible repo) > > This is true pretty much for every component we have right now as you can see > in gerrit. > > Now I guess you could argue that we should file a sub project proposal for > each of those repos but I am not sure if e.g. creating two repos for Check > cookbooks and Check environment files is really a decision which needs TSC > input. That could perfectly be handled by the project team. After all we are > trusting the project team to write the code so why not trust them with this? > > Honestly, my preferred mode of oversite in general is to provide information > that may be relavent and then defer to the guys doing the work. > So please take my comments in that spirit ;) > > When I see repo proliferation a couple of things come to mind for me: > 1) Is that really part of one project with one set of committers? Or is > that a new subcommunitee with a new set of committers (or likely to be). > In my mind, its much easier in a multi-repo environment to miss the "Hey, > that's actually different committers involved and should probably be a new > project" mark. > 2) Repo splits have costs both way. Multiple repos make it harder for folks > to check out all the code, but easier to grab just one corner of it. > Multiple repos make builds more complex, but faster. > e > > My past experience has been that TSCs are at their best when they ask > projects to *consider* questions, express that they have thought about them, > but then defer broadly to the guys on the ground (a projects committers). > > Do you have thoughts for how that might be done in this situation? > > Ed > > > So in my mind this will either lead to: > > A.) unnecessary red tape overhead > B.) people combining things into a single repo because they don?t want to do > the red tape. > > (and believe me I know red tape ?.). Probably you get a bit of both. > > > Oliver > > > On Apr 21, 2017, at 12:07 PM EDT, Ed Warnicke wrote: > > > > Oliver, > > > > For my edification, can you give an example or two of where a well scoped > > project would set up multiple repos? > > > > Ed > > > > On Fri, Apr 21, 2017 at 8:47 AM, SPATSCHECK, OLIVER (OLIVER) > research.att.com> wrote: > > I have another question on the charter. I just noticed that a project (or > > sub project) and a repo are the same thing. I find this to be sub optimal. > > In my mind a project is a well defined scope of work. A repo has to do with > > how to optimize my code management. Am I the only one with the concern > > that binding the two will force people into sub optimal repo structures? > > > > Thx > > > > Oliver > > ___ > > ONAP-TSC mailing list > > ONAP-TSC at lists.onap.org > > https://lists.onap.org/mailman/listinfo/onap-tsc > > > >
[onap-tsc] Updated TSC Charter
That was also my comment on the charter. Projects should be able to setup multiple repos for their scope, e.g. code, documentation, ... and for multiple components separately managed in repos. Thanks, Bryan Sullivan | AT -Original Message- From: SPATSCHECK, OLIVER Sent: Friday, April 21, 2017 8:47 AM To: Christopher Donley (Chris) Cc: Dhananjay Pavgi ; Stephen Terrill ; SULLIVAN, BRYAN L ; onap-tsc at lists.onap.org; Ed Warnicke Subject: Re: [onap-tsc] Updated TSC Charter I have another question on the charter. I just noticed that a project (or sub project) and a repo are the same thing. I find this to be sub optimal. In my mind a project is a well defined scope of work. A repo has to do with how to optimize my code management. Am I the only one with the concern that binding the two will force people into sub optimal repo structures? Thx Oliver
[onap-tsc] Project proposal training material
Brian, Yes, the OPEN-O wiki template is available here: https://wiki.open-o.org/display/REL/Wiki+Proposal+Template if you want to adapt it for ONAP. FYI, the project lifecycle document is contained inside the TSC Charter. Chris From: Brian Hedstrom [mailto:brian.hedst...@oamtechnologies.com] Sent: Friday, April 21, 2017 8:28 AM To: Christopher Donley (Chris) Cc: onap-tsc at lists.onap.org Subject: Re: [onap-tsc] Project proposal training material Chris, Was there a Project proposal Wiki template page in https://confluence.open-o.org/? If so, I could easily duplicate this page into https://wiki.onap.org/ It would be good to create a new templates Wiki section for the various artifacts for a project lifecycle, as well as a lifecycle info or tutorial page. Brian On Thu, Apr 20, 2017 at 9:26 AM, Christopher Donley (Chris) mailto:Christopher.Donley at huawei.com>> wrote: Team, As we discussed on today?s TSC call, here is a presentation from OPEN-O on how to put together a project proposal. While we haven?t specifically discussed the format for ONAP proposals, I expect it will be similar (ODL, OPNFV, OPEN-O, and FD.IO<http://FD.IO> all share a common format with minor variations). Hope this helps, Chris ___ ONAP-TSC mailing list ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org> https://lists.onap.org/mailman/listinfo/onap-tsc -- Brian Hedstrom Founder/CEO OAM Technology Consulting LLC oamtechnologyconsulting.com<http://oamtechnologyconsulting.com> brian.hedstrom at oamtechnologies.com<mailto:brian.hedstrom at oamtechnologies.com> 720-470-7091 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/745d9747/attachment.html>
[onap-tsc] Project proposal training material
On 04/20/2017 08:26 AM, Christopher Donley (Chris) wrote: > Team, > > As we discussed on today?s TSC call, here is a presentation from OPEN-O > on how to put together a project proposal. While we haven?t > specifically discussed the format for ONAP proposals, I expect it will > be similar (ODL, OPNFV, OPEN-O, and FD.IO all share a common format with > minor variations). May I humbly request that the project proposal templates _not_ be PPT files like Open-O was using but a more simple wiki page like OpenDaylight, OPNFV, and FD.io all do? I personally find it painful to have to open up PPT files, not least because it's technically a proprietary format, but mostly because the files are invariably larger than they have a reason to be. -Andy- -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: <http://lists.onap.org/pipermail/onap-tsc/attachments/20170421/571092a2/attachment-0001.sig>
