You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PeriLib project is now undergoing development as a way to address the various shortcomings in the I2Cdevlib project. The goal of this project is to greatly expand the possibilities for how the library can be used, and to fix problems like repository organization, issue tracking and versioning, IDE integration, inconsistent and challenging multi-platform support, underlying I2C HAL code limitations, and others. I invite you to check out the detailed project announcement here on the new Discourse forum:
The original I2Cdevlib website, repository, and forums will remain online and continue as before (which is to say, mostly just coasting along). Thousands of people use these resources, and shutting them down or going into read-only mode would be counterproductive. However, please keep project-specific topics only on the relevant forum: I2Cdevlib discussions go on its forums or repository, while PeriLib discussions go on the other site. Obviously there will be some cross-talk for practical reasons, but just try to avoid getting help or support for either project in the other's community.
I am kicking this off with an open invitation to people who have contributed to the I2Cdevlib project in the past (initially just those with multiple commits). You are logically the first ones to ask about collaborating on this new project. However, please do not feel obligated to accept or even respond to this request unless you're genuinely interested in this new effort. But if you are, feel free to comment on this issue or on the forum post linked above about whatever area(s) you might wish to contribute. Also note that opening a discussion does not mean that you're committing to anything; it's fine if you poke around a bit and ultimately decide not to participate.
I'm asking this way because it's abundantly clear to me that the I2Cdevlib project was/is as successful as it is largely because of contributions from other people, and it was largely due to my own lack of foresight that it has as many problems as it does. I'd rather not make that mistake again.
Hello all,
The PeriLib project is now undergoing development as a way to address the various shortcomings in the I2Cdevlib project. The goal of this project is to greatly expand the possibilities for how the library can be used, and to fix problems like repository organization, issue tracking and versioning, IDE integration, inconsistent and challenging multi-platform support, underlying I2C HAL code limitations, and others. I invite you to check out the detailed project announcement here on the new Discourse forum:
https://community.perilib.io/t/perilib-i2cdevlib-reborn/15
The original I2Cdevlib website, repository, and forums will remain online and continue as before (which is to say, mostly just coasting along). Thousands of people use these resources, and shutting them down or going into read-only mode would be counterproductive. However, please keep project-specific topics only on the relevant forum: I2Cdevlib discussions go on its forums or repository, while PeriLib discussions go on the other site. Obviously there will be some cross-talk for practical reasons, but just try to avoid getting help or support for either project in the other's community.
I am kicking this off with an open invitation to people who have contributed to the I2Cdevlib project in the past (initially just those with multiple commits). You are logically the first ones to ask about collaborating on this new project. However, please do not feel obligated to accept or even respond to this request unless you're genuinely interested in this new effort. But if you are, feel free to comment on this issue or on the forum post linked above about whatever area(s) you might wish to contribute. Also note that opening a discussion does not mean that you're committing to anything; it's fine if you poke around a bit and ultimately decide not to participate.
I'm asking this way because it's abundantly clear to me that the I2Cdevlib project was/is as successful as it is largely because of contributions from other people, and it was largely due to my own lack of foresight that it has as many problems as it does. I'd rather not make that mistake again.
Whatever you decide...happy coding!
The text was updated successfully, but these errors were encountered: