Skip to content

Post Extant Journal Guidelines as they are publicly available and dereferenceable.  #10

@augustfly

Description

@augustfly

While I would like for my PR including the AAS software guidelines (#9) to include our internal informal behaviors or describe what we are evolving towards or listing what we do behind the curtain of the editorial process, I think that it is better for all Example Guidelines to be dereferenceable to public documents.

So... what is posted in 54c592f is super unclear to me. It is in a partial form and could be made to match https://www.elsevier.com/journals/astronomy-and-computing/2213-1337/guide-for-authors for clarity. I'd ask that it also be labeled as "Author" guidelines, pulling editorial/peer review practices out into a separate document.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions