We should have a JIRA project for "Platform" right?

Continuing the discussion from Open Web Apps Tutorial, and adding the module to the Platform:

We have a JIRA project for “Reference Application”. We should have one for “Platform” also. E.g. https://issues.openmrs.org/browse/TRUNK-4806 really belongs there, rather than in the TRUNK JIRA project.

If there’s no opposition to this I’ll request a project from helpdesk next week.

TRUNK really needs to be renamed entirely in my opinion.

3 Likes

Generally, issue trackers are tied to code repositories. (Both within OpenMRS and in other open source projects.) Would there be a new repo for Platform?

Isn’t Platform only release packaging? The individual components - core and bundled modules have their own repositories. So I don’t see why we need a platform repository. Unless there really is code that’s bundling the modules or something. CI settings? or something I don’t see about the release process?

Yes, I think CORE is the appropriate JIRA project name. But that was debated once before and I don’t recall a decision was ever made

+1 for CORE

I like COMMON too.

The github repo for the platform is at https://github.com/openmrs/openmrs-distro-platform

1 Like

I think last time we discussed this everyone wanted to change it, but it was a showstopper that you couldn’t change a project’s key in JIRA.

I just (executively) changed the name to “OpenMRS Core”, though the key is stiil TRUNK. I see that JIRA now lets you change this, but warns that it will require reindexing, so I’ll ask the infrastructure team to do that. (And I’ll wait for @burke’s opinionated opinion about what they key should be.)

Yes, we have a small amount of release packaging code. E.g. this is where the change would need to be made to bundle in the owa module. And it is its own repo. (And this is why I don’t personally feel like “OpenMRS Core” is the right place for the ticket I created.)

1 Like

Just to make sure, will old issue urls still work and be redirected to new ones? Like will going to https://issues.openmrs.org/browse/TRUNK-4571 lead to /CORE-4571 or whatever?

+1 renaming TRUNK to CORE

We have now created a JIRA project for the platform, at: https://issues.openmrs.org/browse/PLAT

The issue mentioned earlier on this thread (adding OWA to the platform) has been moved to https://issues.openmrs.org/browse/PLAT-1

Thanks Helpdesk!

The decision was made to convert to CORE, but before the edit project key feature was added to JIRA… so it never got done. Renaming TRUNK to CORE could happen anytime (the sooner the better), IMHO.

Yes. Any URLs to existing TRUNK tickets will forward to the corresponding CORE ticket. Numbers should stay the same. Even REST calls to TRUNK urls should still work. There appear to be a few places that need updating per the edit project key documentation (e.g., entity links, agile board filters).

Personally, I would prefer this be renamed to https://github.com/openmrs/openmrs-platform, since the platform isn’t really a distribution. “Distribution” connotes a branded, content-ready application, not a platform.

1 Like

As the JIRA project admin, if you’d like to send in a help desk case for this, we can add it to the work queue. :slightly_smiling:

Hopefully this was the ticket: https://issues.openmrs.org/browse/TRUNK-3686

1 Like