Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      story #10403 have consistent repositories listing interface between Git and Subversion
    Actions
    Summary
    Empty
    have consistent repositories listing interface between Git and Subversion
    Empty

    As both services now have the same pattern (servral repositories / project) and almost have the same informations displayed (name, last access, settings) it makes sense to align them with the same UI:

    • Same columns with the same informations
    • Same place and behaviour for repository creation
    Empty
    Patricia Carrasco (pcar), Emilio Palmiero (empa), Benjamin Dauton (bdauton_enalean), Stephan Bill (stephanbill)
    Status
    Empty
    Canceled
    Development
    • [ ] Does it involves User Interface? 
    • [ ] Are there any mockups?
    • [ ] Are permissions checked?
    • [ ] Does it need Javascript development?
    • [ ] Does it need a forge upgrade bucket?
    • [ ] Does it need to execute things in system events?
    • [ ] Does it impact project creation (templates)?
    • [ ] Is it exploratory?
    Empty
    Details
    #10403
    Manuel Vacelet (vaceletm)
    2018-09-14 15:24
    2017-07-04 16:57
    4510

    References
    Artifact links
    Empty
    Referencing story #10403

    Artifact Tracker v5

    story #10408 have a burning parrot git repository list
    Referenced by story #10403

    Artifact Tracker v5

    epic #10400 Tuleap Beau Git
    Display settings

    Follow-ups

    User avatar
    Manuel Vacelet (vaceletm)2018-09-14 15:24

    There are no short term plan to switch svn to burning parrot, let's close this one for now

    • Status changed from Ready (stalled) to Canceled
    • Category set to
    User avatar
    Manuel Vacelet (vaceletm)2017-07-04 17:02

    @bdauton ,

    With the recent discussions about the "BurningParrotification" of Git service (art #10400), I think we should think about the svn plugin service page.

    However, would that make sense to align them, so having the svn repository listing with Burning Parrot them, and when one browse the svn repository to fallback to FlamingParrot ?

    I have hard time to figure out if the switch would be really a bad user experience.

     

    • Acceptance criteria
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • CC list Benjamin Dauton (bdauton_enalean) added
    • Permissions set to