ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: hsbt@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:90815] [Ruby trunk Misc#15486][Assigned] Default gems README.md
Date: Sat, 29 Dec 2018 23:20:07 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-75993.20181229232005.c6a1c66bf4d41c35@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15486.20181229121234@ruby-lang.org

Issue #15486 has been updated by hsbt (Hiroshi SHIBATA).

Status changed from Open to Assigned
Assignee set to hsbt (Hiroshi SHIBATA)

----------------------------------------
Misc #15486: Default gems README.md
https://bugs.ruby-lang.org/issues/15486#change-75993

* Author: zverok (Victor Shepelev)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
While working on [Ruby Changelog](https://bugs.ruby-lang.org/issues/15485), I noticed the following.

A lot of parts of stdlib is extracted currently into "default gems". This, in my understanding, means (amongst other things) their development is now in separate repositories on GitHub, and their development is semi-independent.

The problem I'd like to emphasize is **their README is unclear** about "what is it". Let's look at ostruct for example: https://github.com/ruby/ostruct. There are two huge problems:
* Stumbling upon this repo, how should one know it is a) a part of Ruby stdlib? and b) the authoritative source of this part (and not a mirror of the code in ruby/ruby repo)?
* There is some basic documentation explaining the usage of the library, but it would NOT be rendered anywhere in the standard library docs, so it is basically useless (which is not obvious for repo contributors).

I believe that for standard library gems the README should look somehow as following:

> This is the development repository of Ruby `ostruct` (`OpenStruct`) standard library.
>
> The library provides an `OpenStruct` data structure, similar to a `Hash`, that allows the definition of arbitrary attributes with their accompanying values. 
>
> Canonical library docs: [OpenStruct](https://ruby-doc.org/stdlib-2.6/libdoc/ostruct/rdoc/OpenStruct.html)
>
> Before participating in the development of `ostruct`, you should know the following: 
> * The development process is standard "fork => commit => pull request"
> * New versions of the standard library are released with new versions of Ruby
> * Versioning policy: ...
> * Code quality policy: ...
>

The last two points should probably link to the common documentation for all "default gems"... Well, as well as the whole text. So, all in all, there should be README template, where only gem names, short descriptions, and links to "canonical docs" are different (and maybe some code structure/contribution details for bigger libraries).

WDYT?



-- 
https://bugs.ruby-lang.org/

  parent reply	other threads:[~2018-12-29 23:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-15486.20181229121234@ruby-lang.org>
2018-12-29 12:12 ` [ruby-core:90803] [Ruby trunk Misc#15486] Default gems README.md zverok.offline
2018-12-29 18:26 ` [ruby-core:90810] " ruby-core
2018-12-29 23:20 ` hsbt [this message]
2018-12-30 10:26 ` [ruby-core:90823] " colby
2018-12-31 14:38 ` [ruby-core:90837] " mail
2019-01-02 22:37 ` [ruby-core:90863] " mail
2019-01-04  6:57 ` [ruby-core:90885] " duerst
2019-01-09 14:38 ` [ruby-core:90948] " mail
2019-01-10  6:10 ` [ruby-core:90970] " duerst
2019-01-10  8:11 ` [ruby-core:90979] " duerst
2019-03-11 12:21 ` [ruby-core:91778] " hsbt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-75993.20181229232005.c6a1c66bf4d41c35@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).