Skip to content

Add Apache license and other community files#29

Open
dbca-serkank wants to merge 2 commits into
uatfrom
feature/license
Open

Add Apache license and other community files#29
dbca-serkank wants to merge 2 commits into
uatfrom
feature/license

Conversation

@dbca-serkank
Copy link
Copy Markdown
Collaborator

No description provided.

Copy link
Copy Markdown

@Cechman-01 Cechman-01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved

@ben3000
Copy link
Copy Markdown
Collaborator

ben3000 commented May 26, 2026

Hi @dbca-serkank, other than some minor spelling/grammar issues, I approve.

For example use "practicable" rather than "practical".

Comment thread .github/copilot-instructions.md Outdated
Copy link
Copy Markdown
Collaborator

@ben3000 ben3000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Completed a brief spelling/grammar review.

Copy link
Copy Markdown
Member

@idabblewith idabblewith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dbca-serkank @ben3000 @Cechman-01

Hi team, confirming with OIM their official position on open sourcing this (as well as other projects). Should hear back tomorrow. Note that from initial discussion it seems that:

  1. copyright automatically applies to DBCA, regardless of license and explicit mention (Aus copyright law)
  2. we can use open source licenses (with approval from system owner, in this case, Rory)
  3. if open sourcing, license should NOT be permissive for public contributions

So, may need an adjustment with CONTRIBUTING etc. so the understanding is clear there

@idabblewith
Copy link
Copy Markdown
Member

Note that OIM are not prepared to provide an official position at this stage, so beyond what was mentioned above, sounds like it's entirely up to us

@dbca-serkank
Copy link
Copy Markdown
Collaborator Author

Note that OIM are not prepared to provide an official position at this stage, so beyond what was mentioned above, sounds like it's entirely up to us

Regardless of DBCA's official FOSS position, I would like to get some guidance regarding "contributions". What do you think our public "contribution" policy should be?

@idabblewith @ben3000 @Cechman-01 @ropable @KellyThomas @xzzy

Currently it's set to "encourage":
https://github.com/dbca-wa/authorisations/pull/29/changes#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055

Here are some options:

  • Encourage public contribution (with guideline)
  • Discourage public contribution
  • Do not provide any context

@ben3000
Copy link
Copy Markdown
Collaborator

ben3000 commented May 29, 2026

It would be nice to think that we could kickstart a developer community around DBCA applications that gave young developers a chance to show their skills by providing PRs on relevant applications. I favour encouraging that, so I favour a clear statement of what DBCA expects and an official position from DBCA on open source code contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants