What should we do?

• Capture demo errors.
• Log to sentry

Why should we do it?

Get insights into issues our toolkits have in user environments before we are hit by those in Cawemo or the Camunda Modeler.

What should we do?

Remove "share with Google Plus" button.

Why should we do it?

It's dead 💀 .

Add a Showcase page that features projects built with the bpmn.io toolkit similarly to: https://nextjs.org/showcase/

What should we do?

Update the project contributors on bpmn.io.

Add @Skaiir and @christian-konrad

Why should we do it?

Reflect current project team.

for v0.5.0

I can't edit diagrams, I just see a zoomable diagram with both chrome and firefox on Ubuntu

What should we do?

Do not dynamically load fonts from google fonts. Use locally cached fonts.

ibm PLEX can specifically be installed directly of npm.

Why should we do it?

Recently found to violate GDPR.

Right now we need to manually update the toolkit versions featured on the website.

Tasks

• Toolkit versions are bumped automatically on releases

Feature our recent escaping "improvements".

Blueprint is this post.

Reason: Pending disclosure.

What should we do?

• Add form-js to the site
• Blog about form-js being there now

Why should we do it?

form-js is a great addition to our tools, will soon be ready to use and should be marketed accordingly.

What should we do?

Make it possible to subscribe to blog changes via RSS feed.

Why should we do it?

Being used where people directly want to subscribe to your content, rather than via social media.

Reproduce:

1. Go to https://demo.bpmn.io/dmn/
2. Create new or open existing diagram

Expected behavior:

1. No error

Actual behavior:

1. Crashes

Related to https://app.camunda.com/jira/browse/SUPPORT-4174.

• bpmn-properties-panel 0.9.0
• cmmn-properties-panel 0.2.0

Related to bpmn-io/form-js#216.

same as camunda bpm fav icon in green/white color

Hello guys,

I'm very curious of project you're developing and wanted to look closer in the code of demo available on http://demo.bpmn.io/ at the moment.

I was trying to get it locally and see how it works debugging the code. So I've downloaded https://github.com/bpmn-io/bpmn.io repo, built and got the http://localhost:9012/ page as expected (same page you can see on http://bpmn.io/) but the link "try out the demo" walks me to url http://demo.bpmn.io/ not the local url.

Could you please tell me how to get the demo.bpmn.io pages run locally to debug? or may be I've missed something to do before that one runs locally?

Your progress on showing bpmn docs is so great I can't wait to see how it works, please let me do it locally.

What should we do?

Update the project contributors on bpmn.io.

Add Alexis + Max (if you are fine with it), make Oguz a past contributor.

Why should we do it?

Reflect current project team.

most can be take from:

http://network.camunda.org/privacy (--> add bpmn.io at the beginning)

http://network.camunda.org/imprint (can be copied without any content change)

• needs to be always accessible (in footer)

Guide people through bpmn-js

• what is bpmn-js
• how to get it
• how to do certain things

not only newsletter (push from our side) but also the ability to ask a question

one option coulb be a google forum, which is easy to find.

Following Story should be possible:

1. Somewhere I find out about bpmn.io
2. I visit the website and have a question
3. I can easily find a way to adress this question to the guy behind bpmn.io

Add the bold sentence to the bpmn.io license. This should clarify that the bpmn.io project logo should be shown whenever the software is used in an application or on a website.

Copyright (c) 2014 camunda Services GmbH

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

The source code responsible for displaying the bpmn.io logo (two green cogwheels in a box) that links back to http://bpmn.io as part of rendered diagrams MUST NOT be removed or changed. When this software is being used in a website or application, the logo must stay fully visible and not visually overlapped by other elements.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Tasks

• Update license on http://bpmn.io
• Update license in bpmn-js
• Update license in dmn-js
• Update license in cmmn-js

In order to ease the development of the different sub-projects/dependencies, we could use different ports as follow:

• bpmn.io on port 9000 (and livereload on 9001)
• diagram-js on port 9010 (and livereload on 9011)
• bpmn-js on port 9020 (and livereload on 9021)
• moddle on port 9030 (and livereload on 9031)
• moddle-xml on port 9030 (and livereload on 9031)

This would require some modifications in the grunt files as well as livereload snippets embedded in the pages.

Note that we could depend on the CI job to trigger deploy, cf. job needs and job uses.

Maybe it makes sense to consolidate both deploy scripts into one and merge it with the CI script?

Originally posted by @nikku in #102 (comment)

What should we do?

Write a blog post on dmn-js@12 release.

Cf. changelog

• Why the changes are introduced
• What is changed
• How to adapt to the breaking changes

Why should we do it?

To communicate changes in the library.

Is your feature request related to a problem? Please describe

With browsers, IDEs and other tools I'm used to a smooth navigation in the diagram / in and out of scopes via MODIFIER + arrow keys. On an app like the BPMN.io demo, Web Modeler or Camunda Modeler I'd assume that such navigation is supported, too.

Describe the solution you'd like

• Navigation forward and backwards in the diagram hierarchy is possible via ALT + arrow keys (Chrome, Sublime Text style)

Describe alternatives you've considered

Do not hook navigation in the diagram. Users need to use the mouse.

Additional context

ALT + arrow keys is the standard shortcut for navigating back and forth in your history in Chrome (Linux) and Sublime Text.

Ask Jakob or Stefan for Details

related to bpmn-io/dmn-js#68

What should we do?

• Migrate to GitHub Actions
• Remove old Jenkins jobs

Why should we do it?

Jenkins pipeline is decommissioned.

http://www.camunda.org/bpmn/tutorial.html
http://www.camunda.org/bpmn/examples.html
http://www.camunda.org/bpmn/reference.html

I'd love a feature that makes it possible to swap two selected elements with automatic sequence/message-flow adjusting. The attached image should make it clear.

What should we do?

We should update the screenshots of the Desktop Modeler at https://bpmn.io/modeler/

Why should we do it?

They are outdated and don't represent our recent improvements.

• Generate index.xml RSS feed based on posts

Several things on the website are not up to date anymore

• authors
• desktop app - refers to Chrome App, no hint about Camunda Modeler
• roadmap - outdated
• library versions

Hi, you could simplify the setup process by adding a new entry inside the scripts property in the package.json. In my projects we're using:

"scripts": {
    "postinstall": "bower install -F"
    // ...
}

Then only npm install would be enough. It's just an enhancement tip.

Hello,
Faced with this error while editing the diagram.
Say, you have a 'CallActivity' and a connection to either 'DataObjectReference' or 'DataStoreReference'. If you change the CallActivity type of the same object to any other one (Task, UserTask etc ...) and try to save it on the backend, you will get the following error:

The content of element 'bpmn2:dataInputAssociation' is not complete. One of '{"http://www.omg.org/spec/BPMN/20100524/MODEL":documentation, "http://www.omg.org/spec/BPMN/20100524/MODEL":extensionElements, "http://www.omg.org/spec/BPMN/20100524/MODEL":sourceRef, "http://www.omg.org/spec/BPMN/20100524/MODEL":targetRef}' is expected

But if you manually remove connection with DataObject... it works just fine.

• add landing page
• add getting started

What should we do?

We should update the date in the footer of the website(s).

Why should we do it?

Show and prove to users and search engines that we are maintaining the website and bpmn.io itself and provide a modern solution continuously.

We should give the bpmn-io-bot a nice icon, as it will start to participate more heavily in our release cycle once bpmn-io/bpmn-js#721 is addressed.

The only element I didn't find was grouping. It would be cool to have it.

Congratulations for the awesome app!!!

Thanks.

What should we do?

• Create a blog post that describe extension points the BPMN 2.0 standard offers (bakes into the BPMN 2.0 schema).
• Describe, how that translates to extensibility (i.e. _Creating element bpmn:Foo is not a good idea`, instead ...).

Why should we do it?

The topic comes up in a regular fashion in the forum where users try to create elements like bpmn:foo and we need to argue why that is not a a good idea.

We should document about Promise support in bpmn-js APIs here: https://bpmn.io/l/moving-to-promises.html

Child of bpmn-io/bpmn-js#812

Can you make an example of process editing (including properties and so on) in HTML? The official website is all implemented in VUE.

Is your feature request related to a problem? Please describe

When I click my name below, I am taken to GitHub.

Describe the solution you'd like

I'd rather see more blog posts of mine.

Describe alternatives you've considered

Do nothing.

Additional context