<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 12, 2013 at 8:34 PM, Pierre-Yves Chibon <span dir="ltr"><<a href="mailto:pingou@pingoured.fr" target="_blank">pingou@pingoured.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Jun 17, 2013 at 02:53:31PM +0200, Pierre-Yves Chibon wrote:<br>
> On Mon, 2013-06-17 at 14:44 +0200, Miroslav Suchý wrote:<br>
> > On 06/17/2013 10:59 AM, Pierre-Yves Chibon wrote:<br>
> > > That's also an option :)<br>
> > > But I would argue for using "view" rather than "details".<br>
> > ><br>
> > > Then we would have:<br>
> > > /coprs/view/<user>/<br>
> > > /coprs/edit/<user>/ # edit the user info (if/when we have one)<br>
> > > /coprs/delete/<user>/ # delete the user entirely<br>
> > ><br>
> > > /coprs/new/<user>/ # create a new repo for this user<br>
> > > /coprs/view/<user>/<repo>/ # view this repo<br>
> > > /coprs/edit/<user>/<repo>/ # edit this repo<br>
> > > /coprs/delete/<user>/<repo>/ # delete this repo<br>
> ><br>
> > But then you can not go back in terms of url. I.e. by deleting trailing<br>
> > part of url you could not go back (which was your original problem).<br>
><br>
> >From view you can but indeed from an edit page you cannot go back to the<br>
> view.<br>
><br>
> I guess having the action at the end might be the easiest then:<br>
> /coprs/<user>/<br>
> /coprs/<user>/edit/ # edit the user info (if/when we have one)<br>
> /coprs/<user>/delete/ # delete the user entirely<br>
><br>
> /coprs/<user>/new/ # create a new repo for this user<br>
> /coprs/<user>/<repo>/ # view this repo<br>
> /coprs/<user>/<repo>/edit/ # edit this repo<br>
> /coprs/<user>/<repo>/delete/ # delete this repo<br>
<br>
I am still interested in this and still willing to implement it.<br>
So what do you think of this proposal?<br>
<br></blockquote><div>My personal opinion is having an action at the end might be tricky especially after a commit.</div><div>I thing we should have sections, for example:</div><div>/coprs/<user>/setttings: this is for user profile settings</div>
<div>/copr/<user>/<repo>/settings : this is for settings to the repo</div><div><br></div><div>the actions can be done within settings without necessarily having to give a URL> makes it cleaner.</div><div>I also think if we are within the repo then actions do not necessarily need to be in URL.</div>
<div><br></div><div>but this is just my opinion. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If we agree, shall I commit or shall I just send pull-request/patches to the<br>
list for review first (as this will change a number of files)?<br>
<br>
Best regards,<br>
Pierre<br>
<br>
_______________________________________________<br>
copr-devel mailing list<br>
<a href="mailto:copr-devel@lists.fedorahosted.org">copr-devel@lists.fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/copr-devel" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/copr-devel</a><br>
</blockquote></div><br></div></div>