Skip to content

Naming of Repositories #1

@Idrinth

Description

@Idrinth

As we just talked about, Repositories should follow a standard. I'd describe our results as follows:

Repositories must start their name with the buisness case handles, followed by the technologie(s) it is meant to be used alongside with.

An example would be Session-PHP-Memcached, handling Sessions via PHP and Memcached.
Similar a Javascript library for easier handling of HTTP-Requests with Json would be named HTTPRequest-Javascript-Json following this rule.

Metadata

Metadata

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