Building Open Source Communities In Higher Education

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    Establish credibility Who are we? Jose starts SLOW DOWN.

    SLOW DOWN

    SLOW DOWN

    Justin will continue talking after this slide.

    Trac is modified BSD version 0.10.4 Elgg is GPL 2 version 0.9.2 All of our new code is GPL2

    Jose takes over after this slide.

    Justin will start talking after this slide, finishing the presentation.

    Friend recommendations Better marketplace support Karma

    Beaversource is for students by students Combining project management with social networking to help bring out the open source in everyone. Not a competition.

    1 Favorite

    Building Open Source Communities In Higher Education - Presentation Transcript

    1. BUILDING OPEN SOURCE COMMUNITIES IN HIGHER EDUCATION Jose Cedeno Justin Gallardo
    2. What you will hear in this talk
      • Online communities
      • How to build and maintain an open source community in higher education
      • What challenges college students face when trying to join OSS projects
      • How we are trying to address some of these problems through Beaversource
    3. What you won't hear in this talk
      • Lots of talk about Facebook, Twitter, Winko and other social networks
      • A magic solution that will work for all communities
      • Only a bunch of statistics or technical paper talk
    4. College students get a degree, but most do not possess the skills to successfully join an open source project The problem:
    5. Challenges That Students Face
      • Most likely lack the following basic OSS development skills:
        • Code repository knowledge
        • Code review knowledge
        • Open Source style documentation
        • Dealing and working with large repository
        • Filing good bug reports
        • Collaborating online with other OSS peers
        • RTFM
    6. Collaboration within OSU
      • At the time that the OSS problem of college students was being worked on at OSU, other people within OSU had similar problems.
      • Departments around OSU wanted an easy way to share code and make it publicly available for other developers at OSU
    7. Our Solution
      • An open source code hosting solution that also combines some of the common social networking features.
      • Make it easy for people to find each other and projects they might be interested
      • Create a safe haven where students do not feel intimidated by feedback.
    8. Our Solution
    9. Features Offered by Other Sites
      • We looked at SourceForge, GitHub, Apache Incubator, and Google Code. They had the features below in common:
        • SCM
        • Wiki
        • Finding people and other projects
        • Forums
        • Mailing lists
        • Bug Tracker
    10. Sandbox Concept
      • We want to provide a sandbox area where students interested in OSS can play around in a supportive environment while learning
      • As a CS freshman advances in his or her degree, they start building a portfolio. The various projects that they have worked on are easily available online
    11. What is Beaversource? http://beaversource.oregonstate.edu
      • An open source program that combines Elgg’s social networking features with Trac’s project management tools
      • A collaboration project between College of Engineering, Central Web Services, University Housing and Dining and Network Engineering at Oregon State University
      • Funding for the project was also provided by an NSF grant
    12. Trac
      • This is a project management written for developers by developers using Python.
      • The features it provides are:
        • Bug tracking
        • Wiki
        • SCM
        • Browsing code online
        • Statistics
    13. Bug Tracker
    14. Browsing Code
    15. Wiki
    16. Project Statistics
    17. Trac Technical Details
      • Runs on Python
      • Postgres backend
      • Multi-project support
      • Automated project creation and management
      • Subversion
      • Using 0.10.x right now, looking to upgrade to 0.11.x
    18. Current Limitations
      • We do not have true multi-project support in Trac
        • Lack of aggregation
          • Tickets
          • Changesets
          • Statistics
      • A new set of users is created when a new project is created
      • We are running an old version of Trac
    19. Why is the social side important?
      • Makes it easy for students to find each other
      • People not aware of CS can use the social site and find out more about CS
      • Projects can communicate with users, have discussions and a more user friendly frontend
      • The profile page of a student becomes their portfolio after a few years
      • We can boost student support using things like Karma
    20. Elgg
      • One of the few open source social networking sites that we can use as a framework.
      • It provides us with the features below
        • Friends
        • Project Profiles
        • Forums
    21. Promoting Projects
    22. User Profile
    23. Browsing Friends
    24. Project Profile
    25. Forums
    26. Marketplace
    27. Tag Cloud
    28. Elgg Technical Details
      • Runs on PHP5
      • Supports MySQL database (we’re using postgres)
      • It provides basic level file caching
      • We are in the process of upgrading from 0.9.x to 1.5
    29. Current Limitations
      • We are running an old version of Elgg which gives us many limitations
        • Limited functionality for forums
        • Limited functionality for project profiles
        • Communities cannot have page
        • Not very polished code or API
    30. Results so far
      • 500+ users
      • 50+ projects
      • Lower level classes are using Beaversource
      • Students are giving us plenty of feedback in the form of bug tickets :)
    31. Giving back to the Community
      • We have provided patches for Elgg in the past
      • As we find bugs, we file them in Elgg’s bug tracker
      • We are providing a patch to Elgg1.5 to support postgres databases
      • We idle and participate in #elgg
    32. Future Plans
      • We are in the process of moving hosts. Beaversource will be hosted by the OSL
      • We are upgrading to Elgg1.5 which will give us better support for user profiles and communities
      • We will be doing a homepage redesign and fixing more UI problems
      • Improve documentation
      • Track website traffic better
    33. More OSS at OSU
      • OSWALD
        • Small device with embedded Linux where students can write and test apps
        • http://beaversource.oregonstate.edu/social/cspfl
      • OSEL
        • Help promote open source in classes, organizes events and newsletters
        • http://osel.oregonstate.edu
    34. More OSS at OSU
      • CWS
        • Deploys many websites and tools for the university using open source programs
        • http://oregonstate.edu/cws
      • OSL
        • Provides hosting for popular open source projects while providing great work experience to students
        • http://osuosl.org
    35. Conclusion
    36. Questions?
      • Jose Cedeno
        • [email_address]
        • http://beaversource.oregonstate.edu/social/cedenoj
      • Justin Gallardo
        • [email_address]
        • http://beaversource.oregonstate.edu/social/gallardj
    37.  
    38. Educator Point of view
      • You have to make it easy for the teacher
      • Documentation and instructions are a must
      • We are not trying to replace the existing tools that the teachers have
    39. Why not just use Facebook?
      • We wanted to integrate the social aspect with the coding
      • Launchpad and Ubuntu are also trying to combine the social and coding aspect
      • We are not trying to compete with facebook
    40. Are we taking students from OSS?
      • Short Answer: No
      • We want to be just a starting point for them
      • As their project grows and they require a more robust infrastructure they may choose to move on to SourceForge or GoogleCode
    41. Why not use git?
      • Trac comes with built-in support for SVN
      • Git does not have as robust or user friendly GUI programs for Windows
      • People can use git-svn

    + jirwinjirwin, 4 months ago

    custom

    360 views, 1 favs, 1 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 360
      • 359 on SlideShare
      • 1 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 3
    Most viewed embeds
    • 1 views on https://www.mturk.com

    more

    All embeds
    • 1 views on https://www.mturk.com

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories