Re: Open Source class... starting tomorrow
On 1/21/17 8:57 AM, Phil Steitz wrote: > On 1/21/17 3:31 AM, Scott Wilson wrote: >> Hi Daniel, >> >> When I taught a first year undergraduate course on FOSS the major syllabus >> topics were: >> >> - Community >> - Communications >> - Governance >> - Issue Tracking >> - Sustainability >> - Version Control >> - Intellectual Property >> >> Each student built a case study on a project they were interested in week by >> week published on Wordpress; e.g. >> >> https://pete1124.wordpress.com/ >> https://thejibrjabr.wordpress.com/ >> >> … etc >> >> I was planning to put the content for the course on Github, but the Moodle >> XML export format doesn’t exactly make it very easy… if its of interest I’d >> be happy to share more! > Personally, I would be very interested in following and maybe > eventually contributing to this. The challenges with collaborating > using Moodle export and/or other ed content specs is an interesting > problem that it would be great to solve. Have you ever done this > before? A colleague pointed me at this [1]. Using something like this to manage source content might make open collaborative development of course content easier. Phil [1] https://git-community.cs.odu.edu/zeil/Course_Website_Management > > Phil >>> On 20 Jan 2017, at 22:16, Daniel Ruggeri wrote: >>> >>> Hi, Phil; >>> That makes sense and I will update the syllabus to reflect the proper >>> terminology. I will also plan to spend a class each on build tools and >>> dependency management as those are both great tooics to include. >>> -- >>> Daniel Ruggeri >>> >>> >>> Original Message >>> From: Phil Steitz >>> Sent: January 18, 2017 8:06:48 AM CST >>> To: dev@community.apache.org >>> Subject: Re: Open Source class... starting tomorrow >>> >>> On 1/17/17 10:58 AM, Phil Steitz wrote: On 1/16/17 5:14 PM, Daniel Ruggeri wrote: > Hi, all; > > Digging up "ancient" history on this one > > https://lists.apache.org/thread.html/28c8decf60ec3c79c97a62c936ec9b816da841eb3fb655144dd219ba@1430955768@%3Cdev.community.apache.org%3E > > > I'm happy to share that tomorrow begins the first day of a class I'm > teaching titled "Open Source Software Development" at University of > Missouri - St. Louis in the Information Systems department. Since this > community shared so many great suggestions to help shape the class, I > wanted to drop a big THANK YOU to everyone. > > > I'd also like to share the working syllabus (pardon the empty spots - > we're going to figure out what our class project looks like and work on > that for most of the second half): > > https://github.com/DRuggeri/OSSClass/blob/master/syllabus.md > > > As with any decent, open project the material can be shaped by your > contributions so don't hesitate to reply here if I missed anything > really important to cover. As the course goes on, I'll be posting > outlines and resources in the repository above. With luck, this could > hopefully become an open curriculum anyone can pick up and teach in any > university setting. First, many, many thanks for doing this, Daniel! I really like the idea of developing open content for use in courses like this. I will keep watching the repo! One thing that I don't see there is build tools / systems and artifact repositories. It is no accident that Ant and Maven were developed @apache. Maybe after the scm discussion, you could add something on making it easy to build checked out code, which is key to making it easy to get involved. That would segway naturally into the evolution of build and dependency management systems. >>> One more thing that occurred to me after I sent above. This may >>> seem like a nit, but I would recommend using the term "Issue >>> Tracker" rather than "Bug Tracker." We use these things as part of >>> the core collaboration machinery and managing bugs is only one thing >>> that we use them for. >>> >>> Phil Phil >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >>> > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Meetups and Swag
Thanks for getting in touch. I've copied Missy, who handles shipping swag for North America. I think Sharan has some on the European side. We'll contact you offlist for shipping details, etc. On Jan 20, 2017 18:29, "Andrew Palumbo" wrote: > Hello, > > > I'm contacting whoever this may concern on behalf of the Apache Mahout PMC > > > I just received some feedback from the Board on the Jan Board report, in > which they mentioned that we should contact dev@community.apache.org > regarding some swag, for the Meetups that our project's team has been doing. > > > In the past 2 -3 Quarters, our team has been doing a large amount of > Meetups and conference presentations in North America and Europe; a > noncomprehensive list of this past quarters' Meetups and talks are as > follows: > > > > 1. Sebastian Schelter presented a poster at Machine Learning Systems > Workshop , NIPS 2016 Dec 10, 2016 - "Samsara: Declarative Machine Learning > on Distributed Dataflow Systems" - https://ssc.io/pdf/poster- > mlsystems.pdf > > > 1. Andrew Palumbo presented "Apache Mahout: Beyond MapReduce" at the > Orange County Big Data Meetup, October, 2016. > > > 1. Trevor Grant presented: "Apache Mahout?! What's Next!" At > > * Chicago Hadoop Users Group, October 2016 > > * Seattle Data Science Meetup, December 2016 > > * San Diego Big Data Meetup, December 2016 > > * Austin Data Meetup, December 2016 > > * DFW Data Science Meetup, December 2016 > > > 1. Andrew Musselman presented: "Apache Mahout?! What's Next!" at > Seattle Data Science Meetup, December 2016 > > > 1. Suneel Marthi presented: "Native and Distributed Machine Learning > with Apache Mahout" - Apache Big Data Europe 2016, Nov 13 2016, Seville, > Spain > > > This cadence of these talks and Meetups have been consistent at least over > the 2 quarters previous to last. > > As I've mentioned, part of the the board's feedback from this past report > was that we contact you and request some Apache Swag. These meetups (and > of course NIPS presentations and papers, as well as ApacheCon) are great > methods of Community outreach for Mahout and Apache in general, and it > seems that it would be a good marketing opportunity for Apache. > > Please do let us know how to proceed, > > Thank You Very Much, > > Andrew Palumbo > > Apache Mahout PMC Chair > > >
contributions and their lifecycle
Just a quick question for anyone who wants to answer or has any advice: Other than the obvious Apache-wide conditions (proper measures for intellectual property, etc.), does anyone have examples of policies for accepting and maintaining (code) contributions to a project? I am thinking here about the kinds of conditions that must obtain for a piece of code to remain viable. For example, in a (non-Apache) project with which I am involved, any contribution must have at least two committers ready to take responsibility for it. If at any time after contribution of a module, that stops being the case, that module starts moving on a road to being deprecated out of the mainline codebase into ancillary curation (a process that can stop and reverse at any time if more committers are willing to join in). So I'm looking for examples of similar conditions to meet for contributions to be accepted, simple rules to measure commitment and community, and on the other end of the lifecycle, examples of conditions that decide when a piece of a project has lost vitality and should be excised from the responsibilities that all committers share. Thanks for any examples, pointers, experiences, thoughts to ponder! --- A. Soroka Apache Jena - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: contributions and their lifecycle
A. Soroka wrote on 1/22/17 5:27 PM: > Just a quick question for anyone who wants to answer or has any > advice: > > Other than the obvious Apache-wide conditions (proper measures for > intellectual property, etc.), does anyone have examples of policies > for accepting and maintaining (code) contributions to a project? I am > thinking here about the kinds of conditions that must obtain for a > piece of code to remain viable. There aren't any Apache-wide policies or guidelines about that (i.e. lifecycle of a module within a project); technical governance is left up to each PMC to decide their own working style. At the whole project level, the board reviews quarterly reports to see that a PMC has at least three PMC members who are present in the project - if not actively developing, at least regularly reviewing the mailing lists. Three PMC members are required to vote on a release needed for a security fix, for example. https://www.apache.org/foundation/board/reporting When a project seems inactive or dips to three of fewer PMC members present, the board will typically ask the PMC to either figure out a plan to add more active PMC members to provide oversight, or to ask the community to consider moving to the Attic. Mature projects with little code/release activity are fine, if that's where their technology cycle is, as long as at least three PMC members are present enough to provide oversight. - Shane > For example, in a (non-Apache) project with which I am involved, any > contribution must have at least two committers ready to take > responsibility for it. If at any time after contribution of a module, > that stops being the case, that module starts moving on a road to > being deprecated out of the mainline codebase into ancillary curation > (a process that can stop and reverse at any time if more committers > are willing to join in). > > So I'm looking for examples of similar conditions to meet for > contributions to be accepted, simple rules to measure commitment and > community, and on the other end of the lifecycle, examples of > conditions that decide when a piece of a project has lost vitality > and should be excised from the responsibilities that all committers > share. > > Thanks for any examples, pointers, experiences, thoughts to ponder! > > --- > A. Soroka > Apache Jena - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: contributions and their lifecycle
On Sun, Jan 22, 2017 at 2:27 PM, A. Soroka wrote: > Just a quick question for anyone who wants to answer or has any advice: > > Other than the obvious Apache-wide conditions (proper measures for > intellectual property, etc.), does anyone have examples of policies for > accepting and maintaining (code) contributions to a project? I am thinking > here about the kinds of conditions that must obtain for a piece of code to > remain viable. > > For example, in a (non-Apache) project with which I am involved, any > contribution must have at least two committers ready to take responsibility > for it. If at any time after contribution of a module, that stops being the > case, that module starts moving on a road to being deprecated out of the > mainline codebase into ancillary curation (a process that can stop and > reverse at any time if more committers are willing to join in). > > So I'm looking for examples of similar conditions to meet for contributions > to be accepted, simple rules to measure commitment and community, and on the > other end of the lifecycle, examples of conditions that decide when a piece > of a project has lost vitality and should be excised from the > responsibilities that all committers share. > > Thanks for any examples, pointers, experiences, thoughts to ponder! As Shane pointed out you need to separate foundation-level governance policies (which are really more about how the community governs itself and its IP) from the project governance polices (which are left to the PMC). Shane gave a great answer on the foundation side. On the project's side the two acronyms that get talked about all the time are RTC and CTR. RTC stands for Review Then Commit and CTR stands for Commit Then Review. As you can guess former requires a certain # of positive votes from reviewers while the later leaves feedback gathering exersize unspecified and relies on committers seeking such feedback when they see it is required and simply committing when they are confident in their changes. Both of these greatly benefit from a robust CI pipeline, but CTR is pretty much predicated on good CI. These are the two most popular choices. Then there's also sorts of CI mechanics that can be thrown in (Gerrit, etc.). Finally, even though I haven't seen it at ASF myself, I've worked in a project where you couldn't commit your own code (well you could technically -- but that would be a faux pas). Somebody else had to do it for you -- thus taking the responsibility for it. This was a more interesting example of creating a social dynamic around the project that made a shared responsibility for the code base much more visceral than I've seen otherwise. It also, effectively, made a notion of a "committer" pretty moot. As a side note, I'll add that this practice also lends itself pretty nicely to a sort of a remote pair programming model -- where the other guy committing the code will also have to think about testing. As you can see, you can get a to a pretty sophisticated (convoluted?) set of policies pretty quickly. So IMHO it is always a good idea to start with something super simple (like CTR or RTC) and then evolve from there. Thanks, Roman. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Hello
Hello Arijit, That is very good to hear, Have you been working with the MapReduce Mahout algorithms? Have you used any of the new Samsara algolrithms? This is where we've been focusing our work; around distributed linear Algebra based frameworks and Algorithms. We're actually just now working on a release which is centered around GPU bindinds and Native Multithreading for Distributed Matrix operations. We also will be introducing a new pipeline based framework for algorithms. We are always looking for contributors so you'd be more than welcomed if you dropped by to say hi :). We do have a blog that we've been hoping to get started but have not had the bandwidth lately It's up but actually empty. Maybe we could discuss a blog entry to talk about how you've used mahout in your work? We are trying to get people to see what the new frameworks have offer. Very nice to meet you, Andy From: ARIJIT DAS Sent: Sunday, January 22, 2017 1:32:29 AM To: dev@community.apache.org Subject: Re: Hello Hi Andy, I am using Mahout for NLP specifically for semantic searching in Indian languages as part of my PhD work...it will be my pleasure to contribute for mahout and also take part in the discussion...with a huge data in hdfs mahout has the capability to help us for decision making...You may share the link of mahout specific forum/blog also (if required)..I will be obliged to conribute. With Regards Arijit On Sun, Jan 22, 2017 at 5:58 AM, Andrew Palumbo wrote: > Hello, > > > I sent an email yesterday regarding swag for Meetups, etc to this list, > thinking that it was an Apache list that was devoted specifically to that > type of thing (i was just going off of a comment automatically sent to me > from the last quarter's board report review).. I've noticed several Emails, > and realized that I was wrong about this just being a place to ask for swag > from. > > > So I just wanted to Introduce myself and say hello. I'm the PMC chair of > Apache Mahout. The Mahout team is a die hard group of all volunteer > committers, devoted to distributed shared nothing machine learning, > centered currently around an abstract Engine neutral set of Distributed > Linear Algebra primitives. We're working currently on a release with GPU > and native multithreaded backed matrix operations, as well as to provide > more caned algorithms. We have no corporate backing, which makes it > challenging at times to keep up; most of us work after our day-jobs. This > also makes us flexible and able to answer to no one but our own PMC when > deciding the best direction for the project to go. > > > So I just wanted to Introduce myself, and give you an overview of our > team. The email that I sent yesterday came off more as an order for Apache > swag.. > > > So, Hello, and have a good weekend, all, > > > Andy >
Re: Hello
Hi, Ted, Thanks very much. Yeah- I really wasn't sure what this list was when i got the email telling me to reach out regarding swag, I'm glad that I found it though. seems like some good discussions going on here. As far as what we need/want, I'm really not sure, Anything would be great to be honest, I've only done one talk personally at the Orange County Big Data Analytics Meetup; there were about 60 people there. It does seem like a great place to Advertise Apache and of course Mahout. I've Also been invited by the co-organizers of that meetup to do a talk at the Orange County Advanced Analytics Meetup, which i Am looking for the time to do after this upcoming release. So really anything would be great, Thanks alot for the offer. Its really been Trevor Grant and Suneel Marthi that have been doing most of the talks. Recently Trevor did the DFW meetup which is pretty large from what I understand. So yeah I'm not sure what is available, but a little swag goes a long way. Thanks, Andy From: Ted Dunning Sent: Sunday, January 22, 2017 1:53:07 AM To: dev@community.apache.org Subject: Re: Hello Andrew, I would be happy to help with this directly. What do you need/want? On Jan 21, 2017 4:28 PM, "Andrew Palumbo" wrote: > Hello, > > > I sent an email yesterday regarding swag for Meetups, etc to this list, > thinking that it was an Apache list that was devoted specifically to that > type of thing (i was just going off of a comment automatically sent to me > from the last quarter's board report review).. I've noticed several Emails, > and realized that I was wrong about this just being a place to ask for swag > from. > > > So I just wanted to Introduce myself and say hello. I'm the PMC chair of > Apache Mahout. The Mahout team is a die hard group of all volunteer > committers, devoted to distributed shared nothing machine learning, > centered currently around an abstract Engine neutral set of Distributed > Linear Algebra primitives. We're working currently on a release with GPU > and native multithreaded backed matrix operations, as well as to provide > more caned algorithms. We have no corporate backing, which makes it > challenging at times to keep up; most of us work after our day-jobs. This > also makes us flexible and able to answer to no one but our own PMC when > deciding the best direction for the project to go. > > > So I just wanted to Introduce myself, and give you an overview of our > team. The email that I sent yesterday came off more as an order for Apache > swag.. > > > So, Hello, and have a good weekend, all, > > > Andy >
Re: Meetups and Swag
Hi Rich and Melissa, Thank you very much, This is really great. Please do contact me. As you can see from my email here and as I mentioned to Ted in another email, It is Trevor Grant and Suneel Marthi that do the most meetups and talks. I can get discuss with them their plans for the upcoming quarters, I've recently discussed this with trevor, and know that he is planning several meetups. I'll be planning a meetup myself With the Orange County Advanced Analytics group in the upcoming quarter. I look forward to hearing from you, Andy From: Rich Bowen Sent: Sunday, January 22, 2017 12:19:24 PM To: dev@community.apache.org; Melissa Warnkin Subject: Re: Meetups and Swag Thanks for getting in touch. I've copied Missy, who handles shipping swag for North America. I think Sharan has some on the European side. We'll contact you offlist for shipping details, etc. On Jan 20, 2017 18:29, "Andrew Palumbo" wrote: > Hello, > > > I'm contacting whoever this may concern on behalf of the Apache Mahout PMC > > > I just received some feedback from the Board on the Jan Board report, in > which they mentioned that we should contact dev@community.apache.org > regarding some swag, for the Meetups that our project's team has been doing. > > > In the past 2 -3 Quarters, our team has been doing a large amount of > Meetups and conference presentations in North America and Europe; a > noncomprehensive list of this past quarters' Meetups and talks are as > follows: > > > > 1. Sebastian Schelter presented a poster at Machine Learning Systems > Workshop , NIPS 2016 Dec 10, 2016 - "Samsara: Declarative Machine Learning > on Distributed Dataflow Systems" - https://ssc.io/pdf/poster- > mlsystems.pdf > > > 1. Andrew Palumbo presented "Apache Mahout: Beyond MapReduce" at the > Orange County Big Data Meetup, October, 2016. > > > 1. Trevor Grant presented: "Apache Mahout?! What's Next!" At > > * Chicago Hadoop Users Group, October 2016 > > * Seattle Data Science Meetup, December 2016 > > * San Diego Big Data Meetup, December 2016 > > * Austin Data Meetup, December 2016 > > * DFW Data Science Meetup, December 2016 > > > 1. Andrew Musselman presented: "Apache Mahout?! What's Next!" at > Seattle Data Science Meetup, December 2016 > > > 1. Suneel Marthi presented: "Native and Distributed Machine Learning > with Apache Mahout" - Apache Big Data Europe 2016, Nov 13 2016, Seville, > Spain > > > This cadence of these talks and Meetups have been consistent at least over > the 2 quarters previous to last. > > As I've mentioned, part of the the board's feedback from this past report > was that we contact you and request some Apache Swag. These meetups (and > of course NIPS presentations and papers, as well as ApacheCon) are great > methods of Community outreach for Mahout and Apache in general, and it > seems that it would be a good marketing opportunity for Apache. > > Please do let us know how to proceed, > > Thank You Very Much, > > Andrew Palumbo > > Apache Mahout PMC Chair > > >
Task #7157841f: Suggested tweets for Apachecon
Greetings - I would like to take up this task if this is still available. Kindly let me know. Thank you -Dev
Re: Hello
On Sun, Jan 22, 2017 at 9:45 PM, Andrew Palumbo wrote: > So yeah I'm not sure what is available, but a little swag goes a long way. > I may have some Mahout stickers. Let me look about. I definitely have Drill and Myriad stickers. Let me know if you want some. I personally don't have anything else.
