<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p>> <span style="font-size: 12pt;">The easiest tweak I can think of would be to add a "Inbox" tab to the Project page. Anyone can then be allowed to submit to the project. Internally, all versions are stored in the same project directory, but the legacy
Versions tab would be changed to filter only the versions which are authored by those with write access, while the Inbox tab would show those without write access.</span></p>
<div><br>
</div>
<div>Side note: An even easier tweak would be uploading your proposals to source.squeak.org/inbox. Maintainers can then integrate them later in the squeaksource.com project and move the version from the inbox to treated. I don't know whether anyone would mind
about this. But a real fork/inbox-per-project solution would be more favorable, of course.</div>
<div><br>
</div>
<div>Best,</div>
<div>Christoph</div>
<p></p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Jakob Reschke <jakres+squeak@gmail.com><br>
<b>Gesendet:</b> Donnerstag, 6. Oktober 2022 09:41:17<br>
<b>An:</b> The general-purpose Squeak developers list<br>
<b>Betreff:</b> Re: [squeak-dev] Fixes for possible abandoned squeaksource.com projects</font>
<div> </div>
</div>
<div>
<div dir="auto">Just to relate with the outside world: GitHub, Bitbucket & Co have "forks" as a solution. Since Monticello is distributed, Squeaksource could offer the same feature.
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">To serve the purpose of reviving abandoned projects, such forks would have to be made easily visible on the original project's page. Because without project admin access, the original project description will obviously not change to point to
the newer repository.
<div dir="auto"><br>
</div>
<div dir="auto">Depending on the implementation it could be nearly the same as the inbox proposal of Chris. Just that forks are not publicly writeable.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">karl ramberg <<a href="mailto:karlramberg@gmail.com">karlramberg@gmail.com</a>> schrieb am Mi., 5. Okt. 2022, 22:45:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Oct 5, 2022 at 10:38 PM Chris Muller <<a href="mailto:asqueaker@gmail.com" target="_blank" rel="noreferrer">asqueaker@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>The easiest tweak I can think of would be to add a "Inbox" tab to the Project page. Anyone can then be allowed to submit to the project. Internally, all versions are stored in the same project directory, but the legacy Versions tab would be changed to
filter only the versions which are authored by those with write access, while the Inbox tab would show those without write access.</div>
</div>
</blockquote>
<div> </div>
<div>+1</div>
<div><br>
</div>
<div>Best,</div>
<div>Karl<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div><br>
</div>
<img alt="ss-inbox-idea.png" width="410" height="212" src="cid:ii_l8w2x7gg0"><br>
<div><br>
</div>
<div>Without the above, since only admin-level can delete submitted versions, and configuration is a separate issue from source code repository, I've started opening up my repositories for public write access. Why did I ever think I wanted to discourage contributions?
It theoretically opens them up for spam attacks, but we haven't seen that with our Inbox.<br>
</div>
<div><br>
</div>
<div> - Chris</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Oct 5, 2022 at 1:01 AM karl ramberg <<a href="mailto:karlramberg@gmail.com" target="_blank" rel="noreferrer">karlramberg@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Hi,</div>
<div>I made a small fix for the RayTracing project.</div>
<div><a title="static project url" href="http://www.squeaksource.com/RayTracing.html" target="_blank" rel="noreferrer">http://www.squeaksource.com/RayTracing.html</a>
</div>
<div>Vector needed to subclass Float32Array instead of FloatArray.</div>
<div><br>
</div>
<div>But the RayTracing project is read only. <br>
</div>
<div><br>
</div>
<div>Do we have a best practice for stuff like this?</div>
<div>I uploaded the fix to my own squeaksource account<br>
</div>
<div><br>
</div>
<div>Best,</div>
<div>Karl<br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
</blockquote>
</div>
<br>
</blockquote>
</div>
</div>
<br>
</blockquote>
</div>
</div>
</body>
</html>