creativecommons / commoners Goto Github PK

So the shortcodes render.

Individuals and institutions should be different.

Hi @robmyers

Vouching is very closely modelled on the Mozilla system. People with emails at creativecommons.org are automatically vouched. You can only vouch other people once you have received three vouches. The maximum is six vouches.

Access to member information is restricted to those with one vouch. This may create a bootstrapping problem - if we need to vouch people but don't know about them.

Does this mean member information is not public, but only accessible by those with at least one vouch? Would it be an issue if we make it publicly accessible?

Replace placeholders for ToS etc.

Based on discussion with Legal.

Applicants should not be able to message people via the site until they are fully Vouched Members.

Disable them on all except those they are needed on.

I think the design mockup it's different here

Add form for Legal Team to track communication with Institutional Applicants and insert this into the Institutional Application Workflow.

We split out the ToS/PP and Charter into separate forms in the Individual Applicant Workflow.

Test these.

Currently the same user can be selected more than once.

Catch this in the form validation handler.

Check that BuddyPress is a good fit and see how close we can get it to what we want with available plugins.

Don't show the Insitituion group for Individuals, and vice versa.

Updating profile information works, but displays this message spuriously.

Looks like a CSS url() path issue.

Add form logic to "Final Approval" to email legal@ or correct address when an Institutional Applicant is ready to be contacted.

To protect privacy.

I've been testing this with a super-user so far. Check that each user role can see the approval pages it should be able to, and cannot see the ones it should not.

showing either logged or not

We now enforce not choosing the same voucher more than once in "Choose Vouchers".

But we do not select the previously selected member name when validation fails because of this.

We will need to modify the code that populates the selects.

We have these, copy them in and add tokens to expand.

Make sure members' full profiles are only visible to logged in, approved members.

"WordPress" isn't descriptive enough.

I'm not sure what though.

/sign-up/individual/ not /sign-up/member/

In the interest of communicating with each other better, @simeonoriko were discussing bringing back some sort of syndicated RSS feed for all the global CC blogs.

What do you think? planet.cc.org currently redirects to the API, but this could be a cool thing to have.

It's in the CSS, but it displays as overridden:

SITE_URL

APPLICANT_PROFILE

Only Individual Members can vouch.

Filter Institutions when building the vouching list for the selects in the Choose Vouchers form.

We should probably cache the list.

Application workflow emails (application confirmation, vouch request, etc.) emails aren't sending.

Investigate and fix.

Change it to "Global Network".

Something is up with their styling:

and:

Hi @robmyers !

I thought it'd be easier to discuss issues here especially since you've added vouching and other key features on the test site.

As you may see in the slides, I think an example of a Chapter page could be like this:

North Pole Chapter

Established: Jan 10, 2018
Public Lead: David Bowie
Members: Americano, Cappuccino, Latte, Lager, Pale Ale
Partners: Coffee Organization, Beer Organization
Contributors: Milk, Water, Cream
Homepage:
Social Media:

In addition to this, we could include the information we used to have in affiliate's wiki page, e.g.:
https://wiki.creativecommons.org/wiki/New_Zealand

Does this make sense?

Develop the test instance of BuddyPress so we can just copy it for the live instance.

It's hidden from users but Admins shouldn't see it either in profiles.

For individuals and institutions.

e.g.:

https://network.creativecommons.org/sign-up/individual/form/

https://network.creativecommons.org/members/robcreativecommons-org/

Currently it seems you can only invite your friends to a group. Would this be easier for security purpose?

Ideally we can avoid making a separate form for Institututions.

I think we're filtering the xprofile groups badly.

Will need to hook code that disables profiles and profile fields.

Match dev version.

They shouldn't be able to edit their WP or BuddyPress profiles.

This may seem weird, but they're meant to be entering information in the forms and we don't want it to go into the main DB tables if they're not approved.

• Directories (must be signed in)
• Sign-up forms (must be signed in)
• Vouching form (must be vouched).

We need to hide some items for everyone, and some just for unvouched users.