MyBB Community Forums

(2017-11-05, 10:22 AM)devs Wrote: [ -> ]Look:: its against license. If some work is licensed under (L)GPL (MyBB is LGPL), any work that is based on MyBB have to be under LGPL.
In other words:: MyBB team has to publish each && every bit of source for everything they create and licence under (L)GPL.

The blog (and the site in general, except for the community forum) is not based upon MyBB so we are not restricted to publish it with the same license.

(2017-11-05, 12:59 PM)Shade Wrote: [ -> ]

(2017-11-05, 10:22 AM)devs Wrote: [ -> ]Look:: its against license. If some work is licensed under (L)GPL (MyBB is LGPL), any work that is based on MyBB have to be under LGPL.
In other words:: MyBB team has to publish each && every bit of source for everything they create and licence under (L)GPL.

The blog (and the site in general, except for the community forum) is not based upon MyBB so we are not restricted to publish it with the same license.

Whats the licence then?

Even if it was based on MyBB and GPL, they don't have to publish anything at all. See the GPL FAQ. ( Can I demand a copy? No. Does the GPL require that source code of modified versions be posted to the public? Also no. )

They could do MyBB 1.10 with tons of improvements in private and only update community.mybb.com with it and never give it to anyone and that would still be okay in terms of license.

reminds be of cpanel but the screenshot of mybb makes the software look bad in comparison to mybb.com

We've made some changes related to how versioning information - now on mybb.com instead of docs.mybb.com - is presented. A brief summary of improvements completed with the 1.8.13 release and planned ones that will go with the redesign:

Quote:

• [consistency]
  Release Notes = the version information page containing all details, in machine-readable YAML format (rendered by GitHub Pages);
  Release Blog Post = the corresponding MyBB Blog entry
  
• [convenience] the Release Blog Posts will contain a short, human-friendly highlights of fixes and/or features
  
• [convenience] the Release Blog Posts will contain a link to the Get Involved page
  
• [convenience] the Release Blog Posts will include thanks to vulnerability reporters if the release contains patches following responsibly disclosed security reports
  
• [transparency] MyBB Team association of then-present members that have reported vulnerabilities will be disclosed
  
• [brevity] the security reports note will be made more compact
  
• [consistency] [brevity] unfixed issues, number of changed entities will be listed in Release Notes only
  
• [brevity] specific upgrade instructions will be removed - users will be pointed to appropriate Docs page instead
  
• [security] [convenience] the Release Notes will link to Verifying Releases
  
• [convenience] the Download page will include links to the Release Notes for the most recent release and a listing of all releases, mentioning update packages being available
  
• [security] [consistency] the Blog Release Posts will no longer point to packages directly, but explicitly point to to the official Download page
  
• [security] [consistency] package checksums will be moved to Release Notes, which will also contain package signatures
  
• Related: [security] the Download page will mention package checksums and signatures being available
  
• Related: [security] [convenience] the Download page and Release Notes will point to GitHub-hosted Releases as an alternative source for package downloads
  
• Related: [convenience] [transparency] Issue milestones will not be automatically bumped, resulting in a more clear range of target issues for specific releases
  

@Devil::

+1 for posting this; you forgot to add team transparency here = no dev-related discussion in hidden forum.

(2017-11-08, 08:33 AM)devs Wrote: [ -> ]@Devil::

+1 for posting this; you forgot to add team transparency here = no dev-related discussion in hidden forum.

That is already the case, and has been for some time now.