<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 14/09/17 05:40, Gonzalo Odiard
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJ+iPVSfypuvajnVcYQHOUptWo99+S9N=1r=y7X4eFcHOY52YQ@mail.gmail.com">
<div>Sebastian want a version of sugar-artwork with his own logo,</div>
<div>he can fork the repository. Sugarlabs repositories should be
managed according with the community rules</div>
<div>and looking for consensus.</div>
<div><br>
</div>
<div>Gonzalo</div>
</blockquote>
Hi Gonzalo,<br>
<br>
As you yourself pointed out in #96, pull requests could be years to
be accepted. The linked "community rules", mention "reviewers" and
"maintainers" who in reality don't review or maintain anymore. Much
less have the guts to make a stand to protect users and downstream's
freedom or even care about it. Such a process have no meaning when <i>nobody
is responsible</i> for the release. I fully assume responsibility
for my actions, as I stand by them and will defend them.<br>
<br>
You are welcome to make a pull request and follow the "community
rules" to get it merged.<br>
<br>
So if OLPC want's to put their trademark in everybody's face, then
the burden of forking should be on them (note: as they already do,
out of frustration with our "community rules" not working).<br>
<br>
If we lack a release manager, then the "Development Team" should
communicate this. The recent release by OLPC of Sugar was a take
over which I won't allow, not while my name is in a contract, and,
more importantly, not while it goes against my principles to force a
potentially abused trademark into every project I love.<br>
<br>
Regards,<br>
Sebastian<br>
</body>
</html>