Difference between revisions of "SoC Ideas Simple Content Manager"
(→Whom to ask about this) |
(typos) |
||
| Line 23: | Line 23: | ||
=Additional information= | =Additional information= | ||
| − | This task would be to develop a front end for the most common SCM that would mask completely the underlying tool and would target people that want to contribute to open source, are not technically inclined, and don't want to learn. This tool would implement a minimal subset of SCM features with the philosophy that the user has the support of | + | This task would be to develop a front end for the most common SCM that would mask completely the underlying tool and would target people that want to contribute to open source, are not technically inclined, and don't want to learn. This tool would implement a minimal subset of SCM features with the philosophy that the user has the support of technical people to do complicated tasks |
the following feature list is here to help understand the use-case for the tool | the following feature list is here to help understand the use-case for the tool | ||
| Line 42: | Line 42: | ||
'''other misc constraints''' | '''other misc constraints''' | ||
| − | * python is the | + | * python is the preferred language (all of wesnoth tool are in python) java could be used too (we already have some java code, so maintainability should be ok) |
* it should be SCM agnostic (the point is to lower the barrier to entry for non-technical users) | * it should be SCM agnostic (the point is to lower the barrier to entry for non-technical users) | ||
* the UI should not be frightening to non-technical people (I.E give some thought to UI design in your proposal) | * the UI should not be frightening to non-technical people (I.E give some thought to UI design in your proposal) | ||
* it should integrate as properly as possible into the OS | * it should integrate as properly as possible into the OS | ||
| − | * it should work on windows, Mac and | + | * it should work on windows, Mac and Linux |
= Whom to ask about this = | = Whom to ask about this = | ||
* Boucman (original idea) | * Boucman (original idea) | ||
Revision as of 07:45, 23 March 2011
| This page is related to Summer of Code 2011 |
| See the list of Summer of Code 2011 Ideas |
| This is a Summer of Code 2011 Idea |
Contents
Description
Create a simple content manager frontend for non-technical users
More info at SoC_Ideas_Simple_Content_Manager
Wesnoth has all sorts of contributors that are not coders (translators, graphists, multiplayer developers, musicians, etc)
A large part of these users don't know how to use content managers (git, svn, etc...) and are not interested in learning. Wesnoth has been looking for a simple frontend to the most common content managers for those developers but none of these are simple enough for our use case.
There are no submitted student proposals for this idea
Additional information
This task would be to develop a front end for the most common SCM that would mask completely the underlying tool and would target people that want to contribute to open source, are not technically inclined, and don't want to learn. This tool would implement a minimal subset of SCM features with the philosophy that the user has the support of technical people to do complicated tasks
the following feature list is here to help understand the use-case for the tool
things the tool might do
- update repository wrt distant repository
- commit to distant repository
- prepare a bundle to attach to a mail
- switch branch
- resolve merge conflicts
- build a report on the underlying SCM situation to allow debugging by someone else
- register as a handler to svn:// and git://
'things the tool shouldn't do
- create a new project (if you want to do that, you should learn the real tool)
- create a new branch (a person with the real tool can do that on the repository for you in the rare case it's needed)
other misc constraints
- python is the preferred language (all of wesnoth tool are in python) java could be used too (we already have some java code, so maintainability should be ok)
- it should be SCM agnostic (the point is to lower the barrier to entry for non-technical users)
- the UI should not be frightening to non-technical people (I.E give some thought to UI design in your proposal)
- it should integrate as properly as possible into the OS
- it should work on windows, Mac and Linux
Whom to ask about this
- Boucman (original idea)