goatslacker / goatslacker/siesta

Name transfer

Open
#3 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Hello,

I noticed your npm package `siesta` been published 8 years ago. It also does not have dependent modules. There are few downloads, I guess those are from your CI system.

We've just released an alpha version of our open-source testing tool, called Siesta. Still on early stage, but we are committed to make Siesta a great testing tool.

https://siesta.works
https://github.com/bryntum/siesta
https://www.bryntum.com/blog/announcing-technical-preview-of-siesta-6/

It is currently published on `npm` as `@bryntum/siesta`. Would you consider re-publishing your package and transferring the `siesta` name to us? That would be very much appreciated.

Please let me know what you think.

Regards, Nickolay

P.S. You can reach me at nickolay@bryntum.com

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing issue #3 and the linked Siesta project and npm package information. Done means the maintainer has decided how to handle the request to re-publish the package and transfer the siesta name, with the issue updated accordingly.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.