From Fedora Project Wiki
m (Fix xdg-apps to xdg-app)
Line 1: Line 1:
= Introduction =
+
= About The Project =
  
 
Fedora Developer Portal would be a new place for developers, providing information about tools, technology and other features that are packaged in Fedora. It would raise awareness about new and existing projects among users.
 
Fedora Developer Portal would be a new place for developers, providing information about tools, technology and other features that are packaged in Fedora. It would raise awareness about new and existing projects among users.
  
= Main Purpose =
+
== Target Audience ==
The project would provide information to developers working on Fedora. To be clear, I am talking about '''developers building *on* Fedora, rather than contributing *to* Fedora'''.
+
The target audience is developers working on Fedora. To be clear, To be clear, I am talking about '''developers building *on* Fedora, rather than contributing *to* Fedora'''.
  
 +
They might be either:
 +
# '''Newcomers''': Either choosing their Linux distribution or looking for information about how to start developing. Also searching recommendations.
 +
# '''Existing Fedora Developers''': Discovering what else Fedora offers and learning how to use it.
 +
# '''Existing Developers''': Learning about how to use their existing open source toolsets on Fedora.
 +
 +
Targeting on developers using Mac or even Windows and deploying to Fedora/CentOS might be considered for later iterations.
 +
 +
== Main Purpose ==
 
The site would help developers to:
 
The site would help developers to:
 
# '''Explore''': What tools and tech Fedora offers? (DevAssistant, Vagrant, Python, Ruby, ...)
 
# '''Explore''': What tools and tech Fedora offers? (DevAssistant, Vagrant, Python, Ruby, ...)
Line 11: Line 19:
 
# '''Deploy''': Which deployment technology should I use? (Copr, Nulecule, xdg-app, Software Collections, OpenShift ...)
 
# '''Deploy''': Which deployment technology should I use? (Copr, Nulecule, xdg-app, Software Collections, OpenShift ...)
  
= Resources =
+
 
 +
= Project Resources =
 +
== Repositories ==
 
* Content Repo - https://github.com/developer-portal/content
 
* Content Repo - https://github.com/developer-portal/content
 
* Website Repo - https://github.com/developer-portal/website
 
* Website Repo - https://github.com/developer-portal/website
 
* Design Mockups Repo - https://github.com/developer-portal/mockups
 
* Design Mockups Repo - https://github.com/developer-portal/mockups
* Project Tracking - http://taiga.cloud.fedoraproject.org/project/fedora-developer-portal
 
* IRC channel - #developer-portal on freenode
 
  
= Milestones & Progress =
+
== Communication ==
 +
* #developer-portal at FreeNode - webchat.freenode.net/?channels=#developer-portal
 +
* Fedora Devel Mailing List - https://lists.fedoraproject.org/mailman/listinfo/devel
 +
 
 +
== Project Tracking ==
 +
* Kanban Board - http://taiga.cloud.fedoraproject.org/project/fedora-developer-portal/kanban
 +
* Tasks + Issue Tracking - part of GitHub repositories mentioned above
 +
 
 +
=== Milestones & Progress ===
 
The project will run in five two-week scrums, started on Jul 16, 2015 and ready to be released on Sept 24, 2015. Expected results at the end of each scrum are as follows:
 
The project will run in five two-week scrums, started on Jul 16, 2015 and ready to be released on Sept 24, 2015. Expected results at the end of each scrum are as follows:
 
* Jul 30, 2015 - Working prototype, testing instance deployed
 
* Jul 30, 2015 - Working prototype, testing instance deployed
Line 25: Line 41:
 
* Sep 10, 2015 - Beta release, Content 100% completed
 
* Sep 10, 2015 - Beta release, Content 100% completed
 
* Sep 24, 2015 - Project ready for release
 
* Sep 24, 2015 - Project ready for release
 +
  
 
= Content =
 
= Content =

Revision as of 11:36, 24 July 2015

About The Project

Fedora Developer Portal would be a new place for developers, providing information about tools, technology and other features that are packaged in Fedora. It would raise awareness about new and existing projects among users.

Target Audience

The target audience is developers working on Fedora. To be clear, To be clear, I am talking about developers building *on* Fedora, rather than contributing *to* Fedora.

They might be either:

  1. Newcomers: Either choosing their Linux distribution or looking for information about how to start developing. Also searching recommendations.
  2. Existing Fedora Developers: Discovering what else Fedora offers and learning how to use it.
  3. Existing Developers: Learning about how to use their existing open source toolsets on Fedora.

Targeting on developers using Mac or even Windows and deploying to Fedora/CentOS might be considered for later iterations.

Main Purpose

The site would help developers to:

  1. Explore: What tools and tech Fedora offers? (DevAssistant, Vagrant, Python, Ruby, ...)
  2. Build: How to use this tech? How it is packaged in Fedora?
  3. Deploy: Which deployment technology should I use? (Copr, Nulecule, xdg-app, Software Collections, OpenShift ...)


Project Resources

Repositories

Communication

Project Tracking

Milestones & Progress

The project will run in five two-week scrums, started on Jul 16, 2015 and ready to be released on Sept 24, 2015. Expected results at the end of each scrum are as follows:

  • Jul 30, 2015 - Working prototype, testing instance deployed
  • Aug 13, 2015 - Design mockups ready
  • Aug 27, 2015 - Design implemented
  • Sep 10, 2015 - Beta release, Content 100% completed
  • Sep 24, 2015 - Project ready for release


Content

Structure

  1. Homepage (Main features of the current Fedora release)
  2. The Tools:
    • DevAssistant
    • Docker
    • Vagrant
  3. The Tech:
    1. Languages:
      • Python
      • Ruby
      • PHP
      • Perl
      • GO
      • C
      • Node.js
      • Java
    2. Database:
      • PostgreSQL
      • MariaDB
      • Sqlite
  4. Distribution & Deployment
    • Copr (RPM)
    • Software Collections (decoupling update cycles from host OS)
    • Nulecule (multi-container network services)
    • xdg-app (containers for desktop applications)
    • Rolekit (package installation & configuration flows)
    • OpenShift (autoscaling network application hosting)
  5. Resources [to download]
    • Docker Images
    • Vagrant Boxes
  6. Blogs
  7. Next Release

Possible Views

  • Web Application (What are the ways of creating a web application on Fedora)
    • Flask
    • Django
    • Ruby on Rails
    • PostgreSQL
    • ...

To be completed...

Example

Ruby

  • Installation (both RPM and upstream)
  • Explain them why we have ruby-mri bin and why we use rubypick
  • Answers to how our Ruby differs from upstream
  • Let users know we have a lot or RubyGems packaged
  • Show them our https://github.com/zuhao/isitfedoraruby
  • Let them know there is something like Fedora Ruby SIG that they can join

Vagrant

  • how to get packaged Vagrant
  • providers
    • libvirt
    • how to run libvirt with vagrant without sudo
  • list of plugins we maintain
  • troubleshooting, how to report problems
  • Fedora Vagrant boxes (links)

"I am a Ruby developer" view

  • combination/listing of pages we have and are relevant
  • Ruby, Rails, Vagrant, docker, DevAssistant would show up