[Xerte-dev] Re: Apereo and Governance

[David Goodwin]

Typos :

"This is aprt of a longer term move to a Flash-less world, and the apge 
types we are likely to remove are going to be those associated with 
Flash-based media that we no longer need."


On 
https://github.com/thexerteproject/xerteonlinetoolkits/wiki/4.-Current-Plans


====


Failed bullet list (I assume) :

In addition to their actions as users, contributors may also find 
themselves doing one or more of the following: • supporting new users 
(existing users are often the best people to support new users) • 
hosting face to face or online events • testing and reporting bugs • 
identifying requirements • providing graphics and web design • 
programming • assisting with project infrastructure • writing 
documentation • fixing bugs • adding features

on 
https://github.com/thexerteproject/xerteonlinetoolkits/wiki/1.-The-Xerte-Project-Community


Otherwise it looks good to me (on a quick skim through)

David.


On 13/10/14 14:08, Julian Tenney wrote:
> Good people,
>
> I have chopped up the governance doc I sent round a few weeks ago, and
> populated the github wiki with it. Now is the opportunity for discussion
> and suggestions, and then I think, we should probably vote to accept it!
> It is a work in progress, largely from the OSS Watch meritocracy
> template, and I am more than happy to make changes to it: however, I do
> feel it represents the project well, and from previous comments it seems
> we are fairly close to a consensus around it:
> https://github.com/thexerteproject/xerteonlinetoolkits/wiki.
>
> I think the github wiki should limit itself to being for contributors
> and potential contributors: how the project works, and how to get
> involved and contribute, the governance model, decision making and all
> that good stuff. I think technical / user focused info (like upgrade
> guides) need to be on the community site (though I’ve kept in there for
> the time being because I didn’t want to delete it).
>
> The Nottingham web site will remain essentially a stub for the project.
>
> Once we complete this, we will tick off a number of items on the Apereo
> project plan:
>
> ·A project governance structure should be created to oversee the project.
>
> ·*Standard voting practices should have been adopted.*
>
> ·The project must have adopted a *conflict resolution policy*.
>
> ·*Release plans* should be developed and executed in public by the
> committers.
>
> Julian
>
>
> This message and any attachment are intended solely for the addressee
> and may contain confidential information. If you have received this
> message in error, please send it back to me, and immediately delete
> it.   Please do not use, copy or disclose the information contained in
> this message or in any attachment.  Any views or opinions expressed by
> the author of this email do not necessarily reflect the views of the
> University of Nottingham.
>
> This message has been checked for viruses but the contents of an
> attachment may still contain software viruses which could damage your
> computer system, you are advised to perform your own checks. Email
> communications with the University of Nottingham may be monitored as
> permitted by UK legislation.
>
>
>
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>

-- 
Pale Purple Ltd

PHP Web application development and support

http://www.palepurple.co.uk
@PalePurpleLtd
07792 380669 / 0845 0046746