Skip to content
Snippets Groups Projects

Evaluating NextCloud as replacement for Sandstorm and SVN

    • Closed (moved) Issue created by Linus Nordberg @linus

    Tracking the progress of evaluating NC.

    cf https://trac.torproject.org/projects/tor/wiki/org/meetings/2019BrusselsAdminTeamMinutes#NextCloudNCasaSandstormandSVNreplacement

    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items 0

    • No child items are currently assigned. Use child items to break down this issue into smaller parts.

    Activity

    • Trac
      Trac @tracbot ·

      Trac:
      Child Ticket(s): #29416 (moved), #29417 (moved), #30869 (moved)

    • Linus Nordberg added component::internal services/service - nextcloud priority::medium resolution::fixed severity::normal status::closed type::project labels

      added component::internal services/service - nextcloud priority::medium resolution::fixed severity::normal status::closed type::project labels

    • Georg Koppen
      Georg Koppen @gk ·

      Trac:
      Cc: N/A to gk

    • anarcat
      anarcat @anarcat ·
      Owner

      I still have to read those minutes, but I can vouch for Nextcloud. It's a huge piece of junk written in PHP, with all the warts you might expect, but it does its job, and it does it well. It integrates well with multiple tools on all platforms thanks to its good WebDAV support and could probably bridge without our LDAP server without problems. Plus the extra features (like contacts and todo lists) might be useful for some people, especially HR/management types.

      It's not really packaged in debian anymore, because of upstream asked for the packages to be removed (it was owncloud, but that was before the nextcloud fork) so there's no out of the box deployment and upgrade strategy. I worked with the riseup folks on running nextcloud in containers and that's a promising approach because they maintain their own docker image, but that's a new stack to learn as well which we might not want to get into. It's just the way I would do it. :)

    • Georg Koppen
      Georg Koppen @gk ·

      I just read sajolida's mail (https://lists.torproject.org/pipermail/tor-project/2019-March/002250.html) and wondered whether we could/should think of NextCloud/Talk replacing our BlueJeans thingy, too...

    • Georg Koppen
      Georg Koppen @gk ·

      Here is a link to a (security conscious and thorough) person's repo who is packaging NextCloud for NixOS (the link got dropped into #tor-project the other day): https://github.com/aszlig/avonc. We might be able to learn something from that for our needs.

    • L
      Linus Nordberg @linus ·
      Author

      Trac:
      Component: Internal Services/Tor Sysadmin Team to Internal Services/Services Admin Team
      Owner: tpa to ln5
      Status: new to accepted

    • L
      Linus Nordberg @linus ·
      Author

      Trac:
      Status: accepted to assigned
      Component: Internal Services/Services Admin Team to Internal Services/Service - nextcloud
      Owner: ln5 to N/A

    • Gaba
      Gaba @gaba ·

      I have been using nextcloud for the last week and so far was working fine (until yesterday). 

      I'm using:

      • the calendar for all my meetings and to schedule and invite people to meetings. This is working much better than storm as it has invites.

      • the circle with shared folders for documents (docs and spreadsheets) that we need to work collaboratbily. This is working much better than storm as we can organize documents/information by team. The spreadsheet does not crash when it has more than 4 sheets...

      The problems I had are:

      • yesterday it was taking a long time to load the calendar or documents. I find that is the main problem I also have sometimes with storm.

      • we need a kanban board (right now we use wekan in storm). It would be useful to test the one that you can install in nextcloud.

      • it would be great to see which folders are shared with a specific circle.

      • i wish the spreadsheet would have a menu in text. is there any way to customize this?

    • L
      Linus Nordberg @linus ·
      Author

      Replying to gaba:

      I have been using nextcloud for the last week and so far was working fine (until yesterday). 

      Thanks for the feedback.

      The problems I had are:

      • yesterday it was taking a long time to load the calendar or documents. I find that is the main problem I also have sometimes with storm.

      I think this was related to something which anarcat fixed. Let us know if it happens again.

      • we need a kanban board (right now we use wekan in storm). It would be useful to test the one that you can install in nextcloud.

      IIUC, Richard took a look at the code and said it looks good enough. I'll ask micah for his opinion as well.

      • it would be great to see which folders are shared with a specific circle.

      Do you mean that you'd like to select a circle and get a list of all folders shared with that circle? I don't know how that can be done.

      Selecting a folder, you can see which circles it's been shared with. But you probably knew that.

      • i wish the spreadsheet would have a menu in text. is there any way to customize this?

      What is a menu in text? Like a drop down menu at the top which could take you to all the "things" which there are currently only little icons for? I don't know.

    • Gaba
      Gaba @gaba ·

      Thanks! Now things are loading fine and Deck is working (although is missing an import/export feature).

      Do we have any thoughts on which one will be the process of adoption of nextcloud? Do we start migrating everything and bringing people in or we will have a moment to decide between storm and nextcloud?

    • Georg Koppen
      Georg Koppen @gk ·

      Replying to gaba:

      Thanks! Now things are loading fine and Deck is working (although is missing an import/export feature).

      Do we have any thoughts on which one will be the process of adoption of nextcloud? Do we start migrating everything and bringing people in or we will have a moment to decide between storm and nextcloud?

      I am not sure I understand your second question, but the plan was to migrate away from storm, which is currently unmaintained and has usability issues to a NextCloud instance we run and maintain, once the evaluation period is over. (And no blockers for that migration showed up)

    • Gaba
      Gaba @gaba ·

      Sounds good gk! That was exactly the question.

      It is not possible to import boards in deck unless the API is available. And we have a few boards in storm/wekan right now that would be good not to have to migrate by hand.

      Can we have the API available for deck? !https://deck.readthedocs.io/en/latest/API

    • Georg Koppen
      Georg Koppen @gk ·

      Replying to gaba:

      Sounds good gk! That was exactly the question.

      It is not possible to import boards in deck unless the API is available. And we have a few boards in storm/wekan right now that would be good not to have to migrate by hand.

      Can we have the API available for deck? !https://deck.readthedocs.io/en/latest/API

      Do you mean for the current NextCloud testing environment or for our own instance later on? For the former to get those things already working today (and in case we don't have the API available yet which I don't have chekced) we'd ask micah. For our own instance, yes, I think that would be smart unless there will be strong security concerns that speak against it (which I currently doubt to be the case).

    • C
      cypherpunks @cypherpunks ·

      Hey folks! They know about you! Do you know about them? https://github.com/xwiki-labs/cryptpad

    • L
      Linus Nordberg @linus ·
      Author

      Todays evaluation meeting, held in #tor-meeting, decided that we should go ahead and replace storm with NextCloud. SVN not clear yet which repos, but NextCloud is to be used irregardless.

      New ticket(s) will be created for next steps.

      Trac:
      Status: assigned to closed
      Resolution: N/A to fixed

    • Trac closed

      closed

    • Trac mentioned in issue #29416 (moved)

      mentioned in issue #29416 (moved)

    • Trac mentioned in issue #29417 (moved)

      mentioned in issue #29417 (moved)

    • Trac mentioned in issue #30869 (moved)

      mentioned in issue #30869 (moved)

    Please register or sign in to reply