Semester of Code
On a related note, the Semester of Code pilot programme is now open; this is a programme coordinating students from a number of different universities who want to work with FOSS projects. If you'd like to mentor students working on your Apache project, follow the sign up info below. -S ~~~ The VALS Semester of Code [1] project is working with European universities and FOSS communities to give students real-world experience working in open source software projects while receiving academic credit. The benefit to your projects will be valuable and hopefully ongoing contributions. VALS will also benefit the wider sector by helping to produce graduates with the skills and experience needed to engage with open development. Our first Semester of Code will involve approximately 75 student placements, starting in September. We would like to invite your organisation to participate in this pilot by offering mentored placements within your projects. If you have participated in Google Summer of Code before, you will find our process similar; we will seek placements for student projects, and will use the a system similar to Google's Melange platform to manage placements. However, VALS differs from Summer of Code in that instead of receiving money for their participation, students will receive academic credit. For this reason the mentors from your project will need to liaise with the student's academic tutor. The VALS project will support this process to ensure it runs as smoothly as possible. We also ensure the admin overhead is minimal. The VALS initiative is a partnership of European universities and SMEs who have been working for several months to plan the pilot of Semester of Code, which will run during the next academic year. We have now reached the stage where we are signing up FOSS projects who are willing to provide mentors. We have already seen interest from smaller, single-company projects to larger software foundations, and would like to see more. If you'd be willing to provide one or more mentored projects, we’d love to talk to you about joining Semester of Code. In return, you’ll get an enthusiastic student providing a valuable contribution to your project. The VALS team will be on hand throughout the project to answer any questions and help unblock communication issues between mentors, students and academic supervisors. To join in the Semester of Code or to simply find out more you can email mark.john...@it.ox.ac.uk, or you can sign up to our mailing list directly by using the web form [1]. More detail about the Semester of Code are available on our FAQ page [2]. If you have any other questions, don’t hesitate to ask on the mailing list, and one of the VALS team will get back to you! 1: https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=VALS-SOC&A=1 2: http://semesterofcode.com/?p=22
Re: A maturity model for Apache projects
On 7 Jan 2015, at 08:55, Bertrand Delacretaz wrote: > On Tue, Jan 6, 2015 at 8:16 PM, Mike Drob wrote: >> ...I understand the value of measuring maturity after a project has left the >> Incubator, but I also don't know that we want to put an additional set of >> checkboxes on projects. Either you're ready to graduate, or you're not > > Agreed, and this model can be a good way to measure that readyness. > > My idea is also to help projects who are created elsewhere and might > want to move to Apache later - having them conform to (parts of) the > model will help. Thats a good angle to consider - in these cases the incoming project is "mature" in at least some sense, but we need to understand the areas where we needs to focus on. It would be worthwhile articulating all these requirements for having the model - what we would use it for, how and why. > > -Bertrand
Re: A maturity model for Apache projects
On 6 Jan 2015, at 17:28, Bertrand Delacretaz wrote: > Hi, > > Creating such a model has been on my todo list for ages, and in a > related discussion on board@ people seem to agree that having this can > be useful. > > So let's start - here's my rough initial list of items: > > Code: open, discoverable, fully public history, documented provenance > Quality: security, backwards compatibility, etc > Contributions: welcome from anyone based on technical quality > License: Apache License, dependencies must not put additional restrictions > Community: inclusive, meritocratic, no dictators, clear documented path to > entry > Discussions and decisions: asynchronous, in a single central place, archived > Decision making: consensus, votes if needed, technical vetoes in the worst > case > Independence: from any corporate or organizational influence > Releases: source code only, notices, long-lived release format > > Related efforts, inspiration: > > http://osswatch.jiscinvolve.org/wp/2014/12/11/open-or-fauxpen-use-the-oss-watch-openness-rating-tool-to-find-out/ The SSMM (Software Sustainability Maturity Model)[1] incorporates "Openness" as one of the sections, the others being "Reusability" and "Capability". The Openness Rating is used to measure the Openness (or freedom) aspect of the project. The OR tool looks at a project from several dimensions: • Legal – the conditions surrounding the project source code. Usually defined within the licence terms. • Standards – the data, communication and other standards used within a project, for example, APIs, protocols, & documentation norms. • Knowledge – the documentation, project information, decisions made, communication archives and any other content related to the project. • Governance – the structure of the organisation that defines who participates in a project and the terms of participation. Includes decision making, and any practical or policy limitations on participation. • Marketplace – the ability for any organisation to build a business around a project. Includes practical, legal and technological limitations to building an open marketplace around the project. Reuse is measured using the Reuse Readiness Rating [2], which incorporates some technical elements. Capability is measured using a subset of CMMI [3], which focusses on process maturity. The three sets of measures are combined to position projects on a scale from 0 (Seed) to 8 (Dispersal)[1]. For our purposes at ASF, we need to limit how much we cover and measure depending on the aims we're trying to meet. I think we also need to discuss whether we expect projects to undertake self-evaluation and reflection, or whether we'd have a process of review involving peers, mentors, shepherds etc. (I presume we don't want to just make hoops for projects to jump through, but instead provide useful tools that help both the projects and the ASF as a whole.) [1] http://oss-watch.ac.uk/resources/ssmm [2] http://oss-watch.ac.uk/resources/reusereadinessrating [3] http://en.wikipedia.org/wiki/Capability_Maturity_Model_Integration > > http://rfc.zeromq.org/spec:16 > > -Bertrand
Re: What might an open source class look like?
On 7 May 2015, at 08:50, Stefan Sperling wrote: > > On Wed, May 06, 2015 at 06:42:48PM -0500, Daniel Ruggeri wrote: >> I think this is really neat and exciting but a challenge at the same >> time. Since the idea was planted in my head w/ the ASF, I thought it >> would be a good idea to float the question here to ask, "What would go >> in a college class about open source?" > > Karl Fogel's book about producing open source software should be a > useful resource: http://producingoss.com/ > The way he describes communities is pretty much how the SVN project > works, which (not incidentally) is how ASF projects ought to work :-) > > Perhaps you can use parts of it as reading material for students. > > Karl is has been working on a second edition since last year. > You can get his work in progress state which should be more up to date > with current practices from http://producingoss.com/vc.html > The first edition is from 2005, so somewhat outdated for today's students. I ran a course for one semester on open source for first-year undergraduate students, partly using Karl Fogel’s book and partly lots of OSS Watch material; the student’s course work was focussed on a project of their choice, which they looked at from a range of viewpoints (governance, community, communications, source control etc). You can get an idea of what the course involved from student’s work, which was all on Wordpress: https://pete1124.wordpress.com/ I’ve been meaning to put the whole course on GitHub for a while now - if anyone would be willing to help me port my Moodle course export into content on Github I’d love to make all the materials available! S signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Open Source class... starting tomorrow
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! > 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 > signature.asc Description: Message signed with OpenPGP using GPGMail
