<div dir="ltr">Hi Nico,<div><br></div><div>A couple other details I forgot:</div><div><br></div><div>1) <a href="http://imagej.net">imagej.net</a> is more than just the wiki. It also serves ImageJ1 content; e.g.:</div><div><br></div><div><a href="http://imagej.net/index.html">http://imagej.net/index.html</a></div><div>- The ImageJ1 home page</div><div><br></div><div><a href="http://imagej.net/ImageJ">http://imagej.net/ImageJ</a></div><div>- A wiki page</div><div><br></div><div>This works via proxying: <a href="http://imagej.net">imagej.net</a> forwards the request to either <a href="http://mirror.imagej.net/">http://mirror.imagej.net/</a> or <a href="http://wiki.imagej.net/">http://wiki.imagej.net/</a> depending on the URL requested.</div><div><br></div><div>2) <a href="http://fiji.sc">fiji.sc</a> has a couple of bells and whistles not present on <a href="http://imagej.net">imagej.net</a>:</div><div><br></div><div>- The Git repository mirrors: <a href="http://fiji.sc/git">http://fiji.sc/git</a></div><div>- The search shortcuts—e.g.: <a href="http://fiji.sc/ImageJ.java">http://fiji.sc/ImageJ.java</a></div><div><br></div><div>For the Git mirrors, my preference would be to put them on GitHub instead.</div><div><br></div><div>For the search shortcuts, we now have <a href="http://search.imagej.net/">http://search.imagej.net/</a> which is hopefully a better search solution overall (though there are pros and cons).</div><div><br></div><div>Regards,</div><div>Curtis</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 24, 2015 at 11:51 AM, Curtis Rueden <span dir="ltr"><<a href="mailto:ctrueden@wisc.edu" target="_blank">ctrueden@wisc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Nico,<span class=""><div><br></div><div><div>> Would it be possible to explain somewhere public the relation between</div><div>> Fiji.sc and ImageJ.net for both visitors and contributors?</div></div><div><br></div></span><div>This is a good discussion to have with the community.</div><div><br></div><div>Up till now, the idea has been that <a href="http://fiji.sc" target="_blank">fiji.sc</a> is more appropriate when giving links to Fiji-specific content (e.g., <a href="http://fiji.sc/Fiji_contribution_requirements" target="_blank">http://fiji.sc/Fiji_contribution_requirements</a>), whereas <a href="http://imagej.net" target="_blank">imagej.net</a> is best for topics relevant to ImageJ in general.</div><div><br></div><div>But, I think it will continue to be a source of confusion moving forward. It might be best if all <a href="http://fiji.sc" target="_blank">fiji.sc</a> URLs simply redirect to <a href="http://imagej.net" target="_blank">imagej.net</a> in the future. What do others think?</div><span class=""><div><br></div><div><div>> It appears these are the same with a different skin</div></div><div><br></div></span><div>That is correct.</div><span class=""><div><br></div><div>> editing a page on Fiji.sc results in a server error</div><div><br></div></span><div>It should work if you click the "Edit source" link. The "Edit" link tries to load the WYSIWYG editor, which is currently broken. That said, I personally always just use <a href="http://imagej.net" target="_blank">imagej.net</a> to edit.</div><div><br></div><div>Regards,</div><div>Curtis</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Fri, Jul 24, 2015 at 11:22 AM, Nico Stuurman <span dir="ltr"><<a href="mailto:nico.stuurman@ucsf.edu" target="_blank">nico.stuurman@ucsf.edu</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div bgcolor="#FFFFFF" text="#000000">
<font size="-1">Would it be possible to explain somewhere public the
relation between Fiji.sc and ImageJ.net for both visitors and
contributors? It appears these are the same with a different
skin, but whereas editing a page on Fiji.sc results in a server
error, editing ImageJ.net is OK. Some explanation to
contributors, for instance in a welcome email after registering
would save time.<br>
<br>
Best,<br>
<br>
Nico<br>
</font>
<pre cols="72"></pre>
</div>
<br></div></div>_______________________________________________<br>
ImageJ-devel mailing list<br>
<a href="mailto:ImageJ-devel@imagej.net" target="_blank">ImageJ-devel@imagej.net</a><br>
<a href="http://imagej.net/mailman/listinfo/imagej-devel" rel="noreferrer" target="_blank">http://imagej.net/mailman/listinfo/imagej-devel</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>