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

Write up a guide / documentation about the plugin system #111

Closed
zenspider opened this issue Jun 14, 2011 · 7 comments
Closed

Write up a guide / documentation about the plugin system #111

zenspider opened this issue Jun 14, 2011 · 7 comments

Comments

@zenspider
Copy link
Contributor

Folks should know what the plugin system is, what it's intended use is, that there are some things it isn't meant to be used for, but also, where to go to ask for help to determine whether something is a good fit for the plugin system

and/or ask for extension points to be added to the plugin system API. I will do some research on my own on this if there is time available and contribute if I end up coming up with anything useful, but please don't let that stop anyone who's actively working on RubyGems from beating me to it.

From: http://rubyforge.org/tracker/index.php?func=detail&aid=29243&group_id=126&atid=578

@ghost ghost assigned zenspider Jun 14, 2011
@ghost ghost assigned drbrain Oct 7, 2011
@zenspider
Copy link
Contributor Author

Assigning to @drbrain for first draft. Please assign back for review/editing.

nobu pushed a commit to nobu/rubygems that referenced this issue Jan 12, 2014
Add specs for '<' and '>' format modifiers in Array#pack
@djberg96
Copy link
Contributor

Any progress?

@copiousfreetime
Copy link
Contributor

There is some very basic documentation in the rubygems plugin guide which ends up getting published on the rubygems site: http://guides.rubygems.org/plugins/

A pull request for in rubygems guides repo would probably be the best.

@ghost
Copy link

ghost commented Nov 26, 2017

I attempted a draft here:
rubygems/guides#198

It's not complete, and most probably contains errors (either about the
plugin system, or english texts correctness), but I can fix and update
it.

what it's intended use is, that there are some things it isn't meant to be used for

This part I'm not sure how to address it, @zenspider would you please
have one or more example about what we shouldn't do with the plugin
API?

@zenspider
Copy link
Contributor Author

6.5 years later? No.

@ghost
Copy link

ghost commented Nov 27, 2017

Sorry I decided to start contributing here only a few days ago :-)
I like to start by oldest entries.

By the way I used your gem graph as an example in the draft I wrote, I
hope you don't mind.

If there are no other concerns, then maybe my changes once merged will
allow to close this issue eventually :-)

@bronzdoc
Copy link
Member

bronzdoc commented Mar 1, 2018

closed by rubygems/guides#198

@bronzdoc bronzdoc closed this as completed Mar 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants