Differences between revisions 8 and 9
Revision 8 as of 2016-03-25 04:28:03
Size: 3744
Editor: AaronDelaney
Comment: Update title and minor fixes
Revision 9 as of 2016-03-25 05:02:40
Size: 4280
Editor: AaronDelaney
Comment: Major changes to schedule
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
  * Implement a native application, or in an SPA, that improves Debsources. Faster load times, a patch editor and a good user experience are all important features. This should include documentation and a test suite.   * Implement a native application, or in an SPA, that improves Debsources accessibility. <<BR>>
    This should include documentation and a test suite.<<BR>>
    Desirable features (one Mandatory, rest optional) include:
   * Faster load times
   * A mobile patch editor
Line 28: Line 32:
  * '''Between 23rd May -> 1st June''': Implement the mobile compliant version of the site, including tests and documentation. This does not include the client side rendering aspect of the project.
  * '''Before Mid Term Evaluation''': Have a clear goal for either the native application or hybrid single page application.
  * '''27th June-> 8th August''': Work on implementing the Single Page application and, perhaps, a mobile-native application.
  * '''23rd May -> 1st June''': Prototype the mobile compliant version of the site, This does not include the client side rendering aspect of the project.
  * '''1st June -> 6th June''': Polish-up the mobile version of the site including tests and documentation and research the next aspect of the project: the client side rendering.
  * '''6th June -> 20th June''': Work on learning the client-side rendering framework while integrating with the API. Prototype and get early feedback on this new front-end.
  * '''20th June - 27th June''': Midterm evaluations!
  * '''28th June -> 11th July''': If working on the native application: start working on that integration and mobile specific features.. If not, add framework for the mobile HTML5 features
  * '''12th July -> 31st July''': Work on integrating these new features to Debsources.
  * '''1st August -> 15th August''': Finish up tests, documentation and finish up.
  • Name: Aaron Delaney

  • Contact:

  • Background:

    • I'm a dedicated self-taught programmer now studying Computational Problem Solving and Software Development in Dublin City University.
      I've quite a bit of web experience behind me, my Github lists a good bit of it. To summarize: lots of python, js. Also one thing that's easy to miss on my github is the wand web-app spell-checker, which is in the 'cpssd/optionals/spellcheck' directory.
      Unlisted is a web-based RSS Reader, that uses a Materalize.css frontend with a node.js web-server and a bunch of back-end tools mostly written in Python, that I'm currently working on as a Semester 2 project with a talanted group at DCU.

  • Project title: Improving Accessibility and front-end of Debsources

  • Project details: Debsources is an important resource in the Debian ecosystem. It provides an entry point to all the Debian source code with useful features and API. Unfortunately it doesn't have support mobiles in any sense. This project will fix this issue.

  • Synopsis:

    • Debsources first needs to made mobile compliant by using a response library like Bootstrap. Specifics will be decided on with help from the mentor.
      The next step is then to rework how the client does rendering using a client side rendering engine - such as Angular or React.
      The final step is to add features such as patch editing that either make use of the advanced HTML5 API's or a native app will be created (with help from a tool like Phonegap) that will provide the API's necessary.

  • Benefits to Debian

    • Debsources is a very useful resource to all Debian developers and this project makes it more accessible than ever.
  • Deliverables:

    • A redesigned Debsources webpage that renders well on mobile, with tests integrated into the Debsources test suite and good documentation
    • Research and figure out (with help from the mentors) whether to take Debsources to a native webapp or to figure out how to implement thefeatures inside the mobile browser.
    • Implement a native application, or in an SPA, that improves Debsources accessibility.

      • This should include documentation and a test suite.
        Desirable features (one Mandatory, rest optional) include:

      • Faster load times
      • A mobile patch editor
  • Project schedule:

    • Before 23rd May: Have a good idea of where to take the project in regards the native application or hybrid single page application.

    • 23rd May -> 1st June: Prototype the mobile compliant version of the site, This does not include the client side rendering aspect of the project.

    • 1st June -> 6th June: Polish-up the mobile version of the site including tests and documentation and research the next aspect of the project: the client side rendering.

    • 6th June -> 20th June: Work on learning the client-side rendering framework while integrating with the API. Prototype and get early feedback on this new front-end.

    • 20th June - 27th June: Midterm evaluations!

    • 28th June -> 11th July: If working on the native application: start working on that integration and mobile specific features.. If not, add framework for the mobile HTML5 features

    • 12th July -> 31st July: Work on integrating these new features to Debsources.

    • 1st August -> 15th August: Finish up tests, documentation and finish up.

  • Exams and other commitments: Nope, but I'll let you know early if anything comes up.

  • Other summer plans: Apart from chill out with my friends in my spare time, got nothing!

  • Why Debian?: I love open source and Debian has been a core part of my computing for years. It also seemed like a friendly community based on the wiki.

  • My previous Debian contributions: As required by this application I submitted a patch to #783461 to the qa-debsources mailing list. Apart from that I've not contributed to Debian.

  • Are you applying for other projects in SoC: Doesn't look like it at this point no :)