Nextcloud 11 overview #745
Comments
|
Do we need to check off anything since you've added check boxes? |
|
@BernhardPosselt when it's done |
Or when it's transferred into an issue ;) |
|
Is there an approx. ETA? |
|
@bonanza123 10 is due in a few days to weeks ETA is when it's done, but new releases usually take around 4-12 months |
|
10 is planned for the week of 22-27 of August. 11 is December timeframe. |
|
I'd love to see more of these linked to issue numbers. I tried searching for a few to add myself, without much luck. |
|
@Bugsbane that will be done this week - we largely have to create those issues still ;-) |
|
@blizzz sharepoint: will it be opensource? If yes, then I could support |
|
@pierrejochem yes |
|
@rullzer 👍 |
|
What about client side encryption? |
You're welcome to help contributing to the client side encryption. Please also note that this ticket is not a "I wish features" list. For that one please create a new issue. |
|
@afunix you can use client side encryption today! Just encrypt your file before uploading it. Or dont upload it at all if its that important ;) Apart from that this is more of a sync client ticket and AFAIK someone began to work on it already however dont expect anything in the near future. If you want this feature then I'd suggest you contact the other guy and start programming ;) |
|
@pierrejochem that'll be awesome! Let's discuss once 10 is out. |
|
@blizzz Yes, that sounds like a good plan. Will it be implemented in the files_external app or a seperate one? Or open for discussion? |
|
It makes most sense to get this right into files_external, as all the components are already there and we just need to hook into it. Except there are strong arguments against it? |
|
@blizzz I'm with you so it had to be there in my opinion too |
|
I'd be interested in helping @nickvergessen with the release announcement, if you're up for that, Nick. I have a background in copywriting. |
The task may be phrased a little strange, what we actually want to do is implement something like a "pull announcements from nextcloud.com/org to your instance". We will do this mostlikely on top of https://github.com/nextcloud/announcementcenter |
|
@Bugsbane but talk to @jospoortvliet :) |
Will do. @jospoortvliet What's the best channel to reach you on? |
|
email me on jos at the nextcloud.com server ;-) Thanks for the offer, help would be awesome! |
|
Please only check off items when they are done, not when they just have their own issue. This is the overview issue. |
|
ownCloud has some problems reliable detect changes in external storage. Are there any plans to address this in issue nextcloud? |
|
@blizzz I'm available at IRC. My nickname is pierrejochem |
|
@pierrejochem Sorry, i managed to catch a flu (thought/hoped it would be a weekend thingy, but no) and need to postpone this unfortunately. 😷
Yes, this is helpful. I be there at any day. Basically, the question what you also want to get out of it. Friday is focused on enterprise use, Sat and Sun are the usual conference parts. These three days are mostly talks and talking (but also workhops), directly hands on hacking are Mon-Thu. For instance, you could take Sun+Mon to have a combination. |
|
@blizzz No problem, get well soon and I hope I can get the sunday. Have to ask my wife. Monday is no problem. |
|
App store is feature complete with regards to the 0.1.0 milestone and will enter the stabilization and translation period. The 0.1.0 deployment will kill the current database , so you will need to re-register. App devs can now also start to upload their own apps. Will keep you updated once the release is deployed |
Isn't it better to wait until the release is deployed before creating accounts and uploading apps if the deployment will kill the current database? Or did I misunderstood something? |
|
Before wiping the DB we should also have nextcloud/appstore#249. I'm looking into this… |
|
@schiessle like you said, app devs should be able to upload their apps after we kill the db :) |
|
Ok, certificates, signatures, documentation and validation is now live (including the db wipe). Just ready for the conf 😎 I'd say we keep off publishing a release until 11 is out. We may still need to adjust the API depending on if people implementing the API in Nextcloud run into issues :) |
I think best is talking at the conf, after the week i am still busy with the conf and would not be so well prepared. Do you have fixed dates when you will be there? |
Is this done @jospoortvliet @nickvergessen? |
@blizzz any chance we can get this? It’s pretty essential for the whole @mentioning and discoverability, especially as we mostly show real names instead of usernames :\ |
It's done, once https://github.com/nextcloud/nextcloud_announcements/blob/master/lib/Cron/Crawler.php#L37 does NOT point to |
|
All the remaining stuff should go into 12, so moving this. |
|
Moved open tasks to #2672 |
Merged
ToDo after review on 2016-11-15
Not finished - delayed to 12
This is a rough list of topics we want to work on for Nextcloud 11. It lists the topic and a person who want to work on it and manage the tasks that are to be done. This is up to change and the exact specs are not set in stone now. Some of these are tiny, others are huge - we'll create issues to explain and expand on them the coming week.
If anybody is interested to help out for a specific topic just contact the listed person 😃 And of course if you want to work on something different: feel free to do so and add yourself to the list 😄
Pls be sure to add a issue number of PR link to what you do/did.
The text was updated successfully, but these errors were encountered: