If limiting the number of TM Project Managers is due to server constraints, this is something we can upgrade. Regarding managing the list of projects, it is also can be made through a tagging system we have been discussing about recently. "Community projects" could the ben easily grouped. I am not sure is the tagging would be able to lead these new jobs to another instanciation if we think it would make sense to have another one (same URl, another URL?)
Regarding promoting new TM creators (=Project Managers) it makes senses to increase their number for the advantages a M job represents and the fact it is not yet used as it could. As I guess there may be some stats about PM (how many jobs already created), it could be interesting to suggest to a new promoted one to start by creating a TM job test, eg on the dev instance. On Tue, Oct 7, 2014 at 2:29 PM, Pierre Béland <pierz...@yahoo.fr> wrote: > Other then trying to control the increasing number of administrators there > are instanciations options possible. > > We could have two instanciations of HOT, one for HOT itself, one for other > organizations. Plus there is always the possibility for any organization to > host it's own Task Manager copy. > > An instanciation system like the Ushahidi Crowdmap could be implemented. > > This way, the list of projects would be more manageable. > > > Pierre > > ------------------------------ > *De :* Kate Chapman <kate.chap...@hotosm.org> > *À :* Severin Menard <severin.men...@gmail.com> > *Cc :* "hot@openstreetmap.org" <hot@openstreetmap.org> > *Envoyé le :* Mardi 7 octobre 2014 9h06 > *Objet :* Re: [HOT] Tasking Manager V2 and Project Managers rights > > Hi Severin, > > I think this is the sort of thing where it would be helpful for the > activation working group to provide some guidance. There was previously an > issue when every admin could make anyone else an admin. The idea was to > have a select group of people that can make project managers. How to use > this software feature in the community interactions is a different issue > though. Just meaning I think it would make sense to have a small group of > people that can be contacted to make tasks. They could then decide if they > were going to make the tasks themselves for example in a situation where > someone really wasn't going to regularly need to use the Tasking Manager or > if someone should be made a project manager to manage things themselves. > > Best, > > -Kate > > On Sun, Oct 5, 2014 at 10:07 AM, Severin Menard <severin.men...@gmail.com> > wrote: > > > > Hi, > > Seems nobody answered to this email. I would be interested to discuss > about it, and know about the current way to add new project managers, I > have sincerely no clue what is the process and when it has been discussed > within the community. Sorry if I missed the thread, would be kind to > provide the link to the documentation about this, I am regularly asked > about this topic and cannot answer. > > Sincerely, > > Severin > > On Wed, Aug 27, 2014 at 11:20 PM, Severin Menard <severin.men...@gmail.com > > wrote: > > Hi, > > Sorry to get back very late on this discussion; I renamed the thread. > > As actually the administrator(s) do not know the potential new Project > Managers, this will not change much the potential issues (that were people > creating consecutive bad TM jobs, or something else?). > I propose that the Project Managers still promote new Project Managers, > but now would briefly introduce the people they promoted to the HOT > community, and following these people would introduce themselves to the > community (and could take the opportunity to put this description on their > OSM profile) and explain what areas (can be from national down to > neighborhood scale) their future TM jobs would cover. Would be a good way > to know better who does what and where. And if a new Project Manager spoils > the TM and complicates the Administrators tasks, the latter will be able > to ask the promoters (easy to find in the email archive who they are) to > teach their nominees. > Thoughts? > > Sincerely, > > Severin > > > > On Thu, Jul 17, 2014 at 1:42 PM, Mikel Maron <mikel_ma...@yahoo.com> > wrote: > > Hi > > Yes, there were acknowledged issues with the previous permissions system. > There are administrators, who can change user permissions; and project > managers, who can create jobs. We should discuss how to manage this now, in > the Activation Working Group perhaps. For the time being, contact an > administrator (pgiraud only for the moment) to add new project managers. > > -Mikel > > * Mikel Maron * +14152835207 @mikel s:mikelmaron > > > On Thursday, July 17, 2014 7:18 AM, Severin Menard < > severin.men...@gmail.com> wrote: > > > > Hi, > > What is the new governance regarding Job creation rights? Seems the former > admins - now project managers cannot extend the rights of job creations to > peers they find skilled enough to make them. Were there issues in the past > with this cooptation system? > > Sincerely, > > Severin > > > On Thu, Jul 17, 2014 at 12:56 PM, Marcos Oliveira < > marcosoliveira.2...@gmail.com> wrote: > > Good job Pierre! > > One question: Now that it's possible, where can we go to work on > translating the OSM Tasking Manager? > > > 2014-07-17 11:55 GMT+01:00 Marcos Oliveira <marcosoliveira.2...@gmail.com> > : > > Good job Pierre! > > One question: Where can we go to work on translating the OSM Tasking > Manager? > > > 2014-07-17 11:44 GMT+01:00 Pierre Béland <pierz...@yahoo.fr>: > > Thanks Pierre > > a lot of new improvements, including translation in various languages, a > greater image, the possibility for public in general to see a task without > being connected. > > For the image link, people are forced to click to see the image license > before they can see the image link. This even if this is a public license. > > For the page layout, we are loosing the page layout options with html tag. > This is an important regression, this in the middle of the Ebola > Activation. Any rapid solution for this? As I said many times, we need this > to better emphasize various aspects and make a better presentation. > > _______________________________________________ > HOT mailing list > HOT@openstreetmap.org > https://lists.openstreetmap.org/listinfo/hot > > > > > -- > Um Abraço, > Marcos Oliveira > > > > > -- > Um Abraço, > Marcos Oliveira > > _______________________________________________ > HOT mailing list > HOT@openstreetmap.org > https://lists.openstreetmap.org/listinfo/hot > > > > _______________________________________________ > HOT mailing list > HOT@openstreetmap.org > https://lists.openstreetmap.org/listinfo/hot > > > > > > _______________________________________________ > HOT mailing list > HOT@openstreetmap.org > https://lists.openstreetmap.org/listinfo/hot > > > > > -- > Kate Chapman > Executive Director > email: kate.chap...@hotosm.org > U.S. mobile: +1 703 673 8834 > Indonesian mobile: +62 82123068370 > > *Humanitarian OpenStreetMap Team * > *Using OpenStreetMap * > *for Humanitarian Response * > *& Economic Development* > web <http://hot.openstreetmap.org/> | twitter <http://twitter.com/hotosm> > | facebook <http://facebook.com/hotosm> | donate > <http://hot.openstreetmap.org/donate> > > _______________________________________________ > HOT mailing list > HOT@openstreetmap.org > https://lists.openstreetmap.org/listinfo/hot > > >
_______________________________________________ HOT mailing list HOT@openstreetmap.org https://lists.openstreetmap.org/listinfo/hot
