Git Product home page Git Product logo

office's Introduction

office's People

Contributors

datenangebot avatar juliushaertl avatar splitt3r avatar

Stargazers

avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar

Forkers

datenangebot

office's Issues

Standardize release process

  • Ask for
    • Office team on the releases org
    • Admin permissions on the office team repos
    • Add nextcloud_release_service as app store co-maintainer
  • Setup github actions for automated releases
    • Deck
      • Add GitHub action to all supported branches
      • Add release key to Nextcloud-releases
      • Publish a first release as a test run
    • Nextcloud Office
      • Add GitHub action to all supported branches
      • Add release key to Nextcloud-releases
      • Publish a first release as a test run
    • Office Online
      • Add GitHub action to all supported branches
      • Add release key to Nextcloud-releases
      • Publish a first release as a test run
    • Text Not needed as released as part of the server release bundles
  • Guided release to go through the release process once together
  • Standardise a way to generate the changelog
    • Github action with workflow trigger to bump version and generate changelog

Prepare first release of a new app

  • Make sure you have the necessary workflow on your https://github.com/nextcloud source repository
  • Make sure your tagged commit also have the workflow
  • Make sure this repository have the proper APP_PRIVATE_KEY secret set
  • Make the nextcloud_release_service user is a co-maintainer of your app on https://apps.nextcloud.com/
  • Make sure you have admin rights to this repository

Pending documentation

  • Prepare your local git checkout to add the release remote
    git remote add release [email protected]:nextcloud-releases/richdocuments.git

Checklist for the pull request

<!-- Example checklist for richdocuments, repo urls and stable branch names might need adjustments -->

## Release pull request
- [ ] Pull latest stable branch `git checkout stableX`
- [ ] Branch off a release branch `git checkout -b release/X.X.X`
- [ ] Bump versions
  - [ ] appinfo/info.xml
  - [ ] package.json
  - [ ] package-lock.json
- [ ] Update changelog (Get list of merged PRs `git log vX.X.Y..HEAD --oneline | grep Merge | grep -v dependabot` where X.X.Y is the previous release version)
- [ ] Commit the version bump and push to origin 
- [ ] Merge release pull request

## Release the app

- [ ] Once merged, checkout the stable branch again `git checkout stableX` and `git pull`
- [ ] Tag a new release `git tag vx.x.x`
- [ ] Push tag
  - [ ] to the main repo: `git push origin vx.x.x`
  - [ ] to the release repo: `git push release vx.x.x`
- [ ] Go to https://github.com/nextcloud-releases/richdocuments/tags
  - [ ] Select the tag that you want to create a release of and click "Create release from tag"
  - [ ] Add the version number to the title and the changelog
  - [ ] Publish the release
  - [ ] Wait for the automation to build the app and to be published to the App Store
    - The status can be checked at https://github.com/nextcloud-releases/richdocuments/actions/workflows/appstore-build-publish.yml
  - [ ] Check that the App Store shows the release https://apps.nextcloud.com/apps/richdocuments

Useful commands for generating a changelog

for pr in $(git log v1.5.7..HEAD --oneline | grep Merge | grep -v dependabot | cut -d " " -f 5 | sed 's/#//g'); do printf " - "; gh pr view $pr | head -n1 | cut -d " " -f 2- | tr -d '\n'; echo " #$pr" ; done

Review background jobs for potential TIME_INSENSITIVE switch

With nextcloud/server#30945 it will be possible to move background jobs to times where the server is less busy. We have some tasks that currently run at a fixed interval, where it might make sense to move them for the chance of yielding better performance.

To do

  • Find out which of our background jobs are not time critical
  • Move them

Affected apps

Add docxf and form mimetypes

ONLYOFFICE/onlyoffice-nextcloud#600.
ONLYOFFICE/onlyoffice-nextcloud@5ff63e0.

  • application/vnd.openxmlformats-officedocument.wordprocessingml.document.docxf
  • application/vnd.openxmlformats-officedocument.wordprocessingml.document.oform

nextcloud/server#30732 (comment).
docxf
oform

An example on how to implement can be found in nextcloud/server#29157 where a similar thing was done for odg files.

  • Register mime types in core/js/mimetypelist.js and resources/config/mimetypemapping.dist.json
  • Add icons
  • Add handling during repair step to update existing files

Test coverage

  • Get an overview on how our test coverage is also distributed between unit/integration/e2e tests
  • Regularly measure the coverage
  • Document how to run tests locally, as especially with collabora or integration/e2e tests this maybe trickier than just running one command
  • Test all the things

Nextcloud 25

Features

Branch off

  • Add new stable branch to translation backports nextcloud/richdocuments#2232
  • Bump CI everywhere
  • Adjust branch protection rules
  • Adjust dependabot

After release

  • Cleanup

Nextcloud 24

Tasks related to the next major release Nextcloud 24

Release schedule

  • 2022-03-17 Server feature freeze
  • 2022-04-14 Server RC1
    • Developer and API change documentation
    • App pre-releases
      • Deck 1.7.0-beta.1
      • Nextcloud office 6.0.0-beta.1
      • Office Online
      • Collectives
  • Branch-off
    • master: Appinfo gets updated versions
    • stable: Appinfo gets updated versions
    • stable: tests run against new stable server branch
    • dependabot: remove outdated stable versions, add new ones
    • discuss stability of tables/callout
  • 2022-04-26 Server final
    • Final app releases
    • Admin documentation
    • User documentation
  • Team retrospective

Whiteboard improvements

  • Implement connecting a separate Spacedeck instance
  • Discuss how to continue with upstream changes
  • Check on actual project maintenance
  • See how and if it could be load balanced between multiple ones
  • Maybe do some basic load testing

Unify app branches

Branch Nextcloud version Min. PHP version deck richdocuments officeonline text
master master (24) 7.3 ✔️ ✔️ ✔️ ✔️
stable23 23 7.3 ✔️ stable23 master ✔️
stable22 22 7.3 ✔️ stable4 master ✔️
stable21 21 7.3 ✔️ stable4 master ✔️
  • deck
    • Move to one stable branch per Nextcloud release
    • rename master to main
  • richdocuments
    • Move to one stable branch per Nextcloud release
    • rename master to main
  • officeonline
    • Move to one stable branch per Nextcloud release (to be reconsidered as currently having a multiversion branch works well)
    • rename master to main
  • text
    • Move to one stable branch per Nextcloud release
    • rename master to main

Deck maintenance releases 1.7.1 / 1.6.3 / 1.5.8

Following the process from #1

  • Deck 1.7.1 (stable24)
    • Release pull request
    • Release build and publish
  • Deck 1.6.3 (stable23)
    • Release pull request
    • Release build and publish
  • Deck 1.5.8 (stable22)
    • Release pull request
    • Release build and publish

Gender neutral language

Nextcloud Office

~/repos/nextcloud/server/apps-extra/richdocuments master jq ".translations | keys" l10n/de.json | ack -i "(users?|participants?|attendees?)"
  "All users can edit documents with {productName} by default. When this setting is active, only the members of the specified groups can edit, whereas the others can only view documents.",
  "At the first use and after an update, each user will get the warning, explaining all the above.",
  "Collabora Online is enabled for all users by default. When this setting is active, only members of the specified groups can use it.",
  "Please choose your nickname to continue as guest user.",
  "Remove user",
  "Show watermark for users of groups",
  "Supported placeholders: {userId}, {userDisplayName}, {email}, {date}, {themingName}",
  "The service will send users documents to Collabora and/or third party demo servers.",
  "The users documents will not be retained by a third party after their session completes except in exceptional circumstances. By using the service, the user gives permission for Collabora engineers to exceptionally use such document data, solely for the purpose of providing, optimizing and improving Collabora Online. Such document data will remain confidential to Collabora and/or any third party providing a demo server.",
  "{productName} is enabled for all users by default. When this setting is active, only members of the specified groups can use it.",
  • Collabora Online

text

deck

officeonline

Collectives

"Share not found for user" : "Freigabe für Benutzer nicht gefunden",

PHP 8.1 compatibility

Collectives feature discovery/comparison

sCheck out especially confluence and xwiki

Some quick findings:

  • page metadata

  • dynamic content

  • Global Templates

  • different parent page types (e.g. blog)

  • Import for migrations from notion/confluence maybe together with integration team

  • Page header images

  • Favorites

Some references:

Maybe beta for enterprise customers, maybe demo customers

  • Clarify how to reach out to customers/prospects with interest/using collectives @juliushaertl
  • Feature gap analysis xwiki
  • Schedule brainstorming at the conference/hackweek open to community, sales, marketing @max-nextcloud
  • Discuss possible enterprise beta program (like with sendent)

External people can't open documents in read-write mode

Observed at c.cn.com (Nextcloud 23.0.0.10)

Steps to reproduce

  1. Share a folder with a office document as public link
  2. Set permissions to "can edit"
  3. Open the link in a browser window where you are not logged in

Result

document can't be opnened

grafik

If I remove the "can edit" open, Collabora Online can open the file in read-only mode.

Expected

external user can open the document and edit it

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.