Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require help to help fix article on MP 2.2. release by Erik #33

Closed
aeiras opened this issue Feb 22, 2019 · 8 comments

Comments

2 participants
@aeiras
Copy link
Contributor

commented Feb 22, 2019

article

I sent a tweet to infoQ

If anyone knows the bloger Erik with twitter @costlow, do reach out. :) thanks

@aeiras aeiras self-assigned this Feb 22, 2019

@aeiras aeiras added the enhancement label Feb 22, 2019

@aeiras aeiras added this to To do in Content Creation via automation Feb 22, 2019

@aeiras aeiras changed the title Require to fix article on MP 2.2. release Require help to help fix article on MP 2.2. release by Erik Feb 22, 2019

@aeiras aeiras moved this from To do to In progress in Content Creation Feb 22, 2019

@aeiras aeiras added the help wanted label Feb 22, 2019

@erikcostlow

This comment has been minimized.

Copy link

commented Feb 25, 2019

Hi, yes I wrote that. I can look at changing it, but it's called "Eclipse MicroProfile," the site's "see the code" goes into Eclipse.org through the Eclipse foundation, and the maven groupId is org.eclipse. This combined with people I have talked to, indicate that it either was Eclipse or the community is ok with using that general moniker for simplicity.
What is a better term here that would be have been apparent from the materials?

@aeiras

This comment has been minimized.

Copy link
Contributor Author

commented Feb 25, 2019

@erikcostlow it is nice to virtually meet you Erik!
Thank you for taking the time to follow up via issue and for considering the MicroProfile Project worthy to compose and share via your infoQ blog.

Your actions via that blog are of great value to MicroProfilers as they help the project be documented better to avoid confusions such as the one you state above.

The EF Team doesn't do any develpment for the projects they house under the umbrella. The EF team job is to provide a neutral ground where individuals and different organizations (JUGs, Vendors, etc) can collaborate. Just as the Apache Software Foundation provides that neutral ground that includes the INFRA to enable OSS to thrive.

Each time, a blog comes with the Foundation ONLY name it cuts the work actually done by the contrubutors of the project.

Thank you for adjusting the blog. Currently, we are adding feedback issues to the MP Marketing Repo on how to make the microprofile website clearer. Should you want to help, please help the write-up. What else you and individuals like you could benefit that can be added to site?

@aeiras

This comment has been minimized.

Copy link
Contributor Author

commented Feb 26, 2019

@erikcostlow I adjusted the MP. 2.2 release first sentence to the announcement using your feedback. Thank you!

  • The MicroProfile Community would like to announce the release of Eclipse MicroProfile 2.2.
@erikcostlow

This comment has been minimized.

Copy link

commented Feb 26, 2019

I'm fine with whatever term you think is clear and appropriate. I looked up how Apache did it with Kafka, and they just used the term "Apache." https://globenewswire.com/news-release/2017/11/01/1172058/0/en/The-Apache-Software-Foundation-Announces-Apache-Kafka-v1-0-0.html
The term "community" seems too broad, as users are also part of the community. The question in this context is, who can officially state what is in X.Y release?
Looking at how Apache did it, the headline could say "Eclipse ..." and then the article (which is not a blog) would say something about volunteers or whatever term you choose. That would delineate between the Eclipse Foundation, and the broader group using the term Eclipse. Using that term, I can try to re-word the first sentence to avoid the word "foundation" which seems to be the point of confusion here.

@aeiras

This comment has been minimized.

Copy link
Contributor Author

commented Feb 26, 2019

@erikcostlow adjusted the blog to: Contributors-- really good feedback Erik, thankYOU!

  • The MicroProfile Contributors would like to announce the release of Eclipse MicroProfile 2.2.
@aeiras

This comment has been minimized.

Copy link
Contributor Author

commented Feb 26, 2019

is it ok for us to close this ticket or do you prefer to confirm the blog adjustments via comments to close the issue? Let me know if there is anything else we could improve and lets do this! :)
@erikcostlow

@erikcostlow

This comment has been minimized.

Copy link

commented Feb 26, 2019

I'm fine with that; I'll see if I can make the change.
It will be helpful if the same term is used for other projects as well, like if the Eclipse Collections team uses the same convention. Similar to how the foundation provides infrastructure, they could also provide this branding.

@aeiras

This comment has been minimized.

Copy link
Contributor Author

commented Feb 26, 2019

I agree with you @erikcostlow-- the simple stardarization on names is SUPER important yet not effectively prioritized as such stuff is left unchecked many times. Self-Police goes into effect as shown with our exchanges. 💯 #sharingIScaring i call that.

Today, in the MP project we are chatting about how to make it easier for new Contributors to help without waisting time trying to figure out how to get started. It goes beyond the Repo. Check conversation if you are interested and participate if you want!

@aeiras aeiras closed this Feb 26, 2019

Content Creation automation moved this from In progress to Done Feb 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.