ClassicPress PetitionsClassicPress Petitions
This is a read-only archive. Post or comment on the live version of this page on our forums.

This is a read-only archive of the previous ClassicPress petitions website.

This archive was made at the end of 2020 when Fider stopped offering a hosted version.

To post a new petition, go to the petitions category on our forums.

23
Set login page logo to be Site Logo

As discussed here.

Grab the Site Logo and set that as the logo on the login screen.

That would be lightweight enough (no extra functionality), while also being beneficial for businesses (regardless of whether they have developers or not).

10
New Settings submenu: Security

I think that it would be nice to have a Security submenu item in settings. It could contain "the basics" that those of us who are paranoid do and/or the reasonable/typical things that popular security plugins do.

I'm not suggesting that you try to duplicate/compete with any given security plugin currently on the market... I'm talking about having some of the basics as checkboxes. Some examples:

  • Remove meta generator tags? (from page head and RSS feeds)
  • Enable XML-RPC? (unticked by default; with help text that briefly describes why you might want/need it, else keep it disabled)
  • Disable File Editing? [i.e.: define( 'DISALLOW_FILE_EDIT', true );]
  • Perhaps an option/button/checkbox to add some of these to .htaccess for the user (but only if Apache is detected): https://codex.wordpress.org/Hardening_WordPress#WP-Includes
  • etc, etc, TBD...
CP Research Plugin
8
Require real identities on ClassicPress.net

This seems to be hinted at already in the Democracy values, but its not being enforced (and should be). To encourage transparency and avoid trolling and spam, real names and photos should be required on all accounts, at least those that contribute to Core contributions and Petitions, etc. This should probably be accompanied by an extremely liberal moderation policy where banning or censoring users is a very rare and exceptional occurrence... allowing users to edit their posts would also encourage transparency (like GitHub does) so they can avoid being held hostage to a certain thread or proposal, etc.

Completed

Moving to the forum as there is no need for a petition for this. Moving discussion here

13
Remove the "Alright Sparky" step during installation

Stopping the installation process to indicate that the settings are correct is needless – if the settings are correct, the installation should simply proceed.

Difficulty: Easy
Request: Modify feature
Request: Remove feature
3
Classicpress plugins module

Maybe is time to start dedicated plugins module director like wordpress.org/plugins/ !
Better sooner than it is too late.
Maybe should be made a "top 1000" of compatible plugins, and made their fork here ... or other solutions, but the plugin directory dedicated to this fork must be made !

Completed

Moving to the forum as there is no need for a petition for this.

2
Encourage development of an official ClassicPress Secretary

Every Non Profit Organization (NPO) has someone who organizes events, marketing plan execution strategies and helps everyone streamline and better organize so people aren't butting heads or repeating efforts. In smaller agencies, we'd call the person a Project Manager. The Secretary would keep meeting minutes (summary notes, record video discussions, etcetera). Goes without saying person would need to be vetted and agreed upon by people above my pay grade, the current Committee or whomever Mr. Bowler thinks would be a good fit. It's putting more structure behind what's being done, how things are done, coordination,etc.

Completed

Moving to the forum as there is no need for a petition for this.

1
Define a Marketing Plan

develop a marketing plan that works in conjunction with senior Committee members (to be worked out or done with them in a conference call or video or series of 2-3 calls) so that efforts are more organized top to bottom. The marketing plan would have strategic approaches or tiers with all of them focused on achieving one objective.

Completed

Moving to the forum as there is no need for a petition for this.

1
ServerPress

The community that ClassicPress seeks to serve is 100% of the community at Desktop Servers "ServerPress."

See:
https://gyazo.com/014fb9fad2128cc89c8ef206714cea87

https://gyazo.com/9ffcbcc6600a86198ef969e688f16d6e

I'm a longtime user. With one-click, I deploy local dev WP sites, which, when complete, I can deploy just as quickly for production. Site sync is now available. It was a game-changer for me when I first used it.

I would very much like to see a contact made with the team at ServerPress so that ClassicPress is an option in the list of WP Blueprints.

I would be happy to make that contact if others vote this idea up.

Completed

No need to have a petition for this.

2
Update the default "Just another..." tagline

The term "Just another ClassicPress site" could be jazzed up a bit... something like "Another great ClassicPress site". The term "just another" always makes me think, "oh, great, not another..."

Difficulty: Easy
Request: Modify feature
2
Add a constant so we know we're on ClassicPress

Presumably, CP users will be using my WP plugins. I like to include inline help forms which allow the site admin to attach additional site data to their message by checking boxes (themes/plugins/versions/etc). One of the checkboxes is labeled "WordPress Version", which will be incorrect when the plugins are installed to CP. I'd like to see a simple constant added to the config file...something like:

const WHATEVER = 'ClassicPress';

or

const IS_CP = true;

Completed

As per James' reply, this already has been implemented :)

2
Code of Conduct for ALL

Since CP aims to break free of all the cruft that is WordPress, one aspect that shouldn't be overlooked is the volunteer staff. Some over at WP don't follow their own guidelines for conduct and it leads to a lot of negative posts and conflict. Please, please, please don't let a few angry individuals take over the place like WP has done. They seem mad at the world and approach everything in an adversarial manner, by default. Given the time they spend on the project, it's impossible to extricate them, so I'd just like to see these types not get their hooks into the community in the first place. I realize it may be impossible to vet people completely, but at the very least, action should be taken. Please don't let an otto or a demboskwi ruin it for everyone.

Completed

Thank you Mike for raising this issue. You can see our Code of Conduct here: https://www.classicpress.net/democracy/#democracy-conduct

In cases where the community feels that a person is legitimately no longer able to fulfill their work in adherence with the Code of Conduct (in the example you give, the people are no longer being good to others) then the democratic process can be followed by creating a petition and a vote to remove them from that position of influence.

Ideally, it wouldn't reach this point as Team Leaders should manage these sorts of issues.

Ultimately, we don't want mini-dictators ruining the experience for everyone and I hope our democratic process will at least enable us to resolve cases such as those you describe.

7
Remove the Akismet Plugin

There are more robust solutions out there for protection against spam, and as this is an Automattic product it makes sense to remove it from a fork perspective.

Difficulty: Easy
Request: Remove feature
15
Remove the "Hello Dolly" plugin

It's the first thing I remove every time I install WordPress!

Difficulty: Easy
Request: Remove feature
10
Replace "Howdy" in the Adminbar

Either change it to something more neutral
OR
make it an option that admins can decide on
OR
remove it altogether

Difficulty: Easy
Request: Modify feature