Projects and Teams Hack-a-thon at DevCon 2018

Document created by afaust Moderator on Nov 29, 2017
Version 1Show Document
  • View in full screen mode

Instructions

For people with a project idea

For each project, you should consider addressing the following:

  • The idea owner(s)
  • A brief description
  • Any prep work for the project, such as developer tools or skills participants should understand

 

We encourage you to keep your project idea short and if necessary provide any additional details in separate document or blog post within the Collaborate space. This may also allow you to coordinate with potential team members via the comments there without being mixed in with any discussions on this page.

 

For people looking to join a project

Please feel free to add your name to any project(s) you are interested in participating. Don't hesitate to add your name to multiple projects if you are considering multiple at this point. We encourage you to use this platform to contact the owner of an idea to discuss any details you are unsure about or even improve upon the idea.

 

Apart from any plans you make with the owner of an idea, you are not bound to actually participate in the project you indicated here. The final teams typically constituate themselves on the day of the event based on in-person presentation of the ideas and other factors...

 

Projects

Community Platform / Engagement

Platform Document Review + Action Plan

Idea owner: Axel Faust

Description: In September 2016 the existing community wiki contents were migrated "as-is" from the old MediaWiki-based system into the Jive community platform. This includes a lot of content that was already marked as obsolete in a bulk operation by Richard Esplin since the Alfresco product had outpaced the community efforts (or lack thereof) to keep the information up-to-date. This information still is the bulk of the "documents" inside the ECM space today and only a few documents have been added since.

As part of this project, the community should review the documents that are currently contained in this platform, determine content that would be important to update / add and define an "action plan" of priorities / topics that should be covered. It may be unrealistic to try to make this platform into a full fledged wiki again (and keep it up-to-date/relevant), but if we can identify areas where documents could provide a significant "added value" to the official documentation, efforts could be much more concentrated and efficient, e.g. considering the "work/points balance".

*Logistically, if we can add a tag to the things you evaluate and deem obsolete, we could move these items to an archived space, pulling them out of the ECM space and moving them down in search results. (Kristen Gastaldo)

Prep work: None really, but it sure does not hurt to look through the existing content and maybe think about what important contents you have been missing before...

Interested parties:

  • TBD

 

Alfresco Content Services

Example ECM/ACS Project

Idea owner: John Doe

Description: TBD

Prep work: TBD

Interested parties:

  • TBD

 

Alfresco Process Services

Example BPM/APS Project

Idea owner: John Doe

Description: TBD

Prep work: TBD

Interested parties:

  • TBD

 

Application Development Framework

Example ADF Project

Idea owner: John Doe

Description: TBD

Prep work: TBD

Interested parties:

  • TBD

Attachments

    Outcomes