generated from plebnet-dev/astrowind
-
Notifications
You must be signed in to change notification settings - Fork 17
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'plebnet-dev:main' into main
- Loading branch information
Showing
11 changed files
with
275 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,93 @@ | ||
--- | ||
publishDate: 2024-03-15T00:00:00Z | ||
title: Best Practices for FOSS Contributors and Maintainers | ||
description: If you're new to contributing and bounty hunting, this is for you. | ||
author: ecurrencyhodler and bitkarrot | ||
image: /src/content/post/_images/opensource.jpg | ||
categories: | ||
- Education | ||
tags: | ||
- contributing | ||
- opinion | ||
- bounties | ||
- stakwork | ||
--- | ||
|
||
## Best Practices for FOSS Contributors and Maintainers: Fostering a Collaborative Ecosystem | ||
|
||
Free and Open Source Software (FOSS) thrives on collaboration, and both contributors and maintainers play crucial roles in sustaining these projects. To ensure a vibrant and ever-growing FOSS ecosystem, it's essential for contributors and maintainers alike to follow best practices that enhance communication, foster a positive environment, and promote continuous learning. | ||
|
||
Also, if you are new to bounty hunting in FOSS, this post is for you. For advice from the experienced and wise, skip to the next section and check out the videos. | ||
|
||
### For FOSS Contributors | ||
|
||
#### Understand the Project | ||
When first attempting to contribute to a team, take the time to listen, ask questions, and understand the context of the project. Align your contributions with the project's goals and values to ensure they are well-received by the community. | ||
|
||
#### View Every Interaction as a Learning Experience | ||
Approach each interaction within the community as an opportunity to learn. Concentrate on contributing value to the project rather than extracting value for yourself. | ||
|
||
#### Identify Pain Points | ||
Focus on addressing significant pain points within the project. Tackling substantial challenges demonstrates your commitment and brings valuable improvements to the software. | ||
|
||
#### Follow Through on Tasks | ||
When you decide to take on a task within a FOSS project, commit to it. Completing assigned tasks not only contributes to the project's success but also builds trust within the community. | ||
|
||
#### Treat Contributions Like an Audition | ||
Consider each contribution as an audition for a leading Broadway role. Put your best self forward, exceeding your normal standards, as the FOSS community can be seen as a stage where your talents are showcased. | ||
|
||
#### Demonstrate Extra Credit | ||
Go beyond the minimum requirements. Show that you can think beyond the scope of the original issue and provide valuable insights. This signals to the community that you are a high-value contributor. | ||
|
||
#### Have a Growth Mindset to FOSS Bounties | ||
There is a growing trend in FOSS projects to offer bounties to work on issues. Do not fixate on the size of the task or the amount offered in the bounties; instead, prioritize the learning opportunities each contribution offers. Sometimes projects or tasks may not work out, and that's okay—every experience is a stepping stone for improvement. | ||
|
||
#### Prioritize Communication | ||
Effective communication is key in any collaborative effort. Keep contributors and maintainers in the loop regarding your progress. Over-communicating is better than leaving others uninformed, and it helps create a transparent and collaborative environment. | ||
|
||
### Advice from the Experienced and Wise | ||
|
||
If you are a new developer, why should you join an existing FOSS project instead of building your own project? From the guy (Matteo Collina) who has [17 Billion NPM downloads](https://youtu.be/4aYQ0QPUikg?feature=shared&t=729) | ||
|
||
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/4aYQ0QPUikg?si=9J2frio8Ho29KqhA&start=731" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> | ||
|
||
“You don’t need to be extremely good to contribute to open source projects, but if you do, more importantly, people will review your code which will make you way way better…. Your skills will skyrocket. “ - Matteo Collina | ||
|
||
“FOSS is essentially like free work experience,..... It’s not really something you can do on your own” - Lane Wagner, Backend Banter | ||
|
||
|
||
### For FOSS Project Maintainers | ||
|
||
#### Clearly Define Requirements | ||
To avoid miscommunication, provide clear requirements and acceptance criteria for tasks. Clarity ensures that contributors understand the expectations and can deliver quality work. | ||
|
||
#### Encourage and Celebrate Work | ||
Acknowledge and celebrate the contributions of contributors. Publicly recognize their efforts, whether through social media shoutouts or other forms of acknowledgment, fostering a positive community atmosphere. | ||
|
||
#### Provide Constructive Feedback | ||
Offer constructive feedback to new contributors. Encourage them to ask questions early and often, creating an environment where learning and improvement are valued. | ||
|
||
#### Set Realistic Timeframes | ||
Give contributors adequate time to close issues and update pull requests. However, strike a balance—don't let issues linger for too long without follow-up. Be proactive and address concerns promptly. | ||
|
||
#### Be Aware of Trolls | ||
In any online community, trolls can emerge. Be vigilant and handle potentially contentious situations before they escalate. Similar to an internet moderator, maintainers should be adept at diffusing tensions and promoting a respectful discourse. | ||
|
||
Effective collaboration within FOSS projects relies on the commitment and synergy between contributors and maintainers. By adhering to these best practices, both groups can create a thriving ecosystem that encourages continuous learning, celebrates achievements, and ultimately results in high-quality open source software. Remember, FOSS is a collective effort where everyone's contribution matters. | ||
|
||
## Some more useful advice | ||
|
||
- Open Source is Not about you - From the Clojure developers and Primeagen | ||
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/H9GkSSWbw4c?si=2u6VJVXOe2E1ql8F" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> | ||
|
||
|
||
- 5 Signs of an Inexperienced Self-Taught Developer [(and how to fix)](https://www.youtube.com/watch?v=B_HR2R3xsnQ) | ||
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/B_HR2R3xsnQ?si=JuYFsmEW9tSdG4pX" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> | ||
|
||
|
||
- Stop solving problems that don't exist - Lessons from a Legend that all new developers should learn from - From the Linus Torvalds. | ||
|
||
<iframe width="560" height="315" src="https://www.youtube.com/embed/EvzB_Q1gSds?si=dAsdlisxP5pKS_vr&start=4" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,100 @@ | ||
--- | ||
publishDate: 2024-2-28T00:00:00Z | ||
title: Member Contributions To Open Source Software - January 2024 | ||
image: /src/content/post/_images/january.png | ||
description: Contributions for the month of January 2024 | ||
category: News and Updates | ||
author: surfersol and bitkarrot | ||
tags: | ||
- events | ||
- monthly meetup | ||
--- | ||
|
||
# Member Contributions for January 2024 | ||
|
||
## About this post | ||
|
||
In no particular order, let's celebrate all the member contributions from Plebnet.DEV to open source software! Contributions are collected by a moderator in the discord every month so be sure to reach out to them before the monthly meetup if you would like to be mentioned on this monthly blog post. If you contributed and we missed it, please make a pull request and we'll be sure to include it here! | ||
|
||
|
||
### Bitkarrot: | ||
|
||
- Delivered [LNBits Scheduler Extension](https://github.com/bitkarrot/scheduler) | ||
- Delivered [LNBits Decoder Extension release](https://github.com/bitkarrot/decoder) | ||
- Worked on [LNBits Scheduler Extension release vetted by LNBits team](https://github.com/bitkarrot/scheduler/) | ||
- Delivered a January 2024 [LNBits workshop](https://github.com/plebnet-dev/Workshops) | ||
- Slides for [LNBits Workshop](https://github.com/plebnet-dev/Workshops/blob/main/LNBitsJan2024Workshop.pdf) | ||
|
||
- Worked on Refactoring Plebnet.dev [Registration](https://github.com/plebnet-dev/website/commit/acc11097aeed49786758c16344b4931d9478beab) | ||
|
||
### Randy McMillian | ||
|
||
- Delivered gnostr [command](https://github.com/gnostr-org/gnostr-command) | ||
- Delivered [gnostr-command-docker](https://github.com/gnostr-org/gnostr-command/blob/master/gnostr-command-docker) | ||
- Working on gnostr command [gnostr: a git+nostr workflow utility](https://command.gnostr.org/) | ||
- Working on [nostr.cooking](https://github.com/github-tijlxyz/nostr.cooking) | ||
|
||
### BitcOinDad | ||
- Working on [Bitcoin Transscripts](https://github.com/bitcointranscripts/bitcointranscripts/pull/387) | ||
- Worked on [https://rates.plebnet.dev/ ERROR](https://github.com/plebnet-dev/website/issues/92) | ||
- Worked on Rates calculator[Fix/issue#2](https://github.com/plebnet-dev/rates/pull/3) | ||
- Working on [Update fiatlist to include additional currencies](https://github.com/plebnet-dev/rates/issues/4) | ||
- Worked on [Updated Past and Upcoming Events Blog Post](https://github.com/plebnet-dev/website/pull/97) | ||
- Worked on [cargo.mk:make:add cargo-b-release command](https://github.com/gnostr-org/gnostr-bits/pull/3) | ||
- Worked on [Gnostr pull request 118](https://github.com/gnostr-org/gnostr/pull/118) | ||
- Worked on [Gnostr Update to v.0.0.17](https://github.com/plebnet-dev/gnostr/pull/1) | ||
- Delivered [Essential Environment Setup](https://github.com/plebnet-dev/website/pull/109) blog post | ||
- [Updated December 2023 Collaborators Blog](https://github.com/plebnet-dev/website/pull/101) | ||
|
||
### XenonFun | ||
- Worked on [PLEBNET-PLAYGROUND / plebnet-playground-docker Commit](https://github.com/PLEBNET-PLAYGROUND/plebnet-playground-docker) | ||
|
||
### BloggingBitcoin | ||
- Working on [ZapButtons](https://github.com/BrutusBondBTC/ZapButtons/commits/main/) | ||
- Worked on [SupernautApp / SupernautFX](https://github.com/SupernautApp/SupernautFX) | ||
- Worked on [ConsensusJ / consensusj](https://github.com/ConsensusJ/consensusj) | ||
|
||
### msgilligan | ||
- Working on [gradle.yml: add macos-14 (aarch64) to the build Matrix](https://github.com/bitcoinj/bitcoinj/pull/3345) | ||
- Working on [gradle.yml, graalvm.yml: gradle/actions/setup-gradle@v3](https://github.com/bitcoinj/bitcoinj/pull/3346) | ||
- Working on [gradle.yml, graalvm.yml: Upgrade multiple actions](https://github.com/bitcoinj/bitcoinj/pull/3347) | ||
- Working on [Add link for Bitcoin Core, add Bisq, Sparrow, bitcoinj](https://github.com/BTCMedia/B24-Open-Source-Program/pull/369) | ||
|
||
## Maintainers contributing to Review and Merging PRs | ||
|
||
### msgilligan | ||
- Reviewed [raise error when flake attribute doesn't exist](https://github.com/hercules-ci/flake-parts/pull/200) | ||
- Reviewed [doc: trivial typo fixes](https://github.com/openjdk/jextract/pull/171) | ||
- Reviewed [Two new service bits](https://github.com/bitcoinj/bitcoinj/pull/3343) | ||
- Reviewed [GitHub Actions upgrade actions to node 20 versions](https://github.com/ConsensusJ/consensusj/pull/155) | ||
|
||
### asherp | ||
- Merged [fix unsafe warning](https://github.com/plebnet-dev/website/pull/102) | ||
- Merged [docker build and run locally](https://github.com/plebnet-dev/website/pull/100) | ||
|
||
### bitkarrot | ||
- Merged [Updated December 2023 Collaborators Blog](https://github.com/plebnet-dev/website/pull/101) | ||
- Merged [Bump axios and @sendgrid/mail](https://github.com/plebnet-dev/website/pull/98) | ||
- Merged [Updated Past and Upcoming Events Blog Post](https://github.com/plebnet-dev/website/pull/97) | ||
- Merged [Bump vite from 4.5.1 to 4.5.2](https://github.com/plebnet-dev/website/pull/96) | ||
- Merged [Refactor registration (WIP)](https://github.com/plebnet-dev/website/pull/95) | ||
|
||
### amsalmeron | ||
- Reviewed [Refactor registration (WIP)](https://github.com/plebnet-dev/website/pull/95) | ||
|
||
|
||
### dependabot (bot for security updates or manual pull requests to easily update vulnerable dependencies) | ||
- Bump aiohttp from [3.8.6 to 3.9.0](https://github.com/lightningames/nostr-telegram/pull/14) | ||
- Bump aiohttp from [3.9.1 to 3.9.2](https://github.com/lightningames/pylnbits/pull/108) | ||
- Bump aiohttp from [3.8.6 to 3.9.2](https://github.com/lightningames/nostr-telegram/pull/16) | ||
- Update all Resource links to [Permalinks](https://github.com/plebnet-dev/website/issues/58) | ||
- Store link on plebnet.dev gated behind [unsafe warning](https://github.com/plebnet-dev/website/issues/89) | ||
- Bump mkdocs-material from [9.5.4 to 9.5.6](https://github.com/lightningames/pylnbits/pull/107) | ||
- Update black requirement from [^23.3 to ^24.1](https://github.com/lightningames/pylnbits/pull/106) | ||
- Bump aiohttp from [3.9.1 to 3.9.2](https://github.com/lightningames/pylnbits/pull/105) | ||
|
||
# Plebnet.dev events / workshops | ||
|
||
### BitcOinDad (moderator) | ||
- Python Blitz: Code and Conquer Weekly (Weekly Event) | ||
- Chill and Chat (Bi-Weekly Event) |
Binary file not shown.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
publishDate: 2027-03-18T00:00:00Z | ||
title: How to use lightning testnet resources | ||
description: Use the lightning faucet and lnbits to get your environment ready for building on lightning. | ||
author: bitkarrot | ||
image: /src/content/post/_images/testnet-lightning.png | ||
categories: | ||
- Education | ||
tags: | ||
- resources | ||
- testnet | ||
- lightning | ||
- bitcoin | ||
- development | ||
--- | ||
|
||
<div style="padding:56.25% 0 0 0;position:relative;"><iframe src="https://player.vimeo.com/video/922801415?badge=0&autopause=0&player_id=0&app_id=58479" frameborder="0" allow="autoplay; fullscreen; picture-in-picture; clipboard-write" style="position:absolute;top:0;left:0;width:100%;height:100%;" title="Plebnet.dev Testnet Lightning Demo video"></iframe></div><script src="https://player.vimeo.com/api/player.js"></script> | ||
|
||
|
||
This is a brief guide on how to use testnet lightning resources at Plebnet.dev. | ||
|
||
- [htlc.me](https://htlc.me) is a lightning testnet faucet. [Testnet.plebnet.dev](https://testnet.plebnet.dev) is a LNBIts testnet instance available to the public.The LNBits testnet account may also be used to fund a local LNBits development instance. | ||
> **Be Sure to return your funds to the htlc faucet when you are done!** | ||
- You can open a channel to our [Testnet CLN Node](https://mempool.space/testnet/lightning/node/03ba00a57cec1cef4873065ad54d0912696274cc53155b29a3b1256720e33a0943) | ||
- If you need help with converting between satoshis, bitcoin and fiat, here is a helpful [rate converter](https://rates.plebnet.dev/). Find more resources [here](https://plebnet.dev/resources) |